api.chargeid.in · v1 · private beta

One API shape across the networks you connect.

Your stations and their live status in one shape, whichever network they’re on. Sessions, and starting or stopping a charge, come through the same API on connections that carry them.

Request API access How connecting works

Normalize network differences once.

Stations, connectors and sessions use the same model regardless of what sits underneath — OCPP, OCPI, UEI or a vendor API.

See what operators run on top of the same API

Same resources. Same units. Same timestamps.

Every response wraps its payload in data. Connector types and statuses come normalized to one vocabulary, power is in kW and timestamps are RFC 3339.

Commands on the same resource

Start a charge with POST /sessions and stop it with POST /sessions/:id/stop — on OCPP chargers, and on vendor platforms that accept remote commands.

api.chargeid.in200 OK

GET/api/v1/stations

Authorization: Bearer cid_live_7Qc…d2

Responseapplication/json

{
  "data": [
    {
      "id": "0b7d4c2e-9a51-4f3e-8c6d-2e1f5a7b9c30",
      "name": "Nexus Charge, Baner",
      "cpoName": "Nexus Charge",
      "location": { "lat": 18.559, "lng": 73.7868 },
      "status": "available",
      "connectorTypes": ["ccs2", "type2_ac"],
      "sessionCount30d": 390
    }
  ]
}

Trimmed to a few fields.

Keys are issued during the private beta.

Tell us what you’re building. We’ll issue a key for your organization and go through the endpoints with your engineer.

Request API access See the platform