One API shape across the networks you connect.
Build on ChargeID with a single, well-documented REST API. Read your stations and their live status, see every session, and start or stop charging — whichever network your chargers are on, in one consistent shape.
Normalize network differences once.
Stations, connectors and sessions use the same model regardless of what sits underneath — OCPP, OCPI, UEI or a vendor 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.
Events, not polling
Subscribe to webhooks for session start and stop, status changes and settlement — so your app reacts the moment something happens on a charger.
Read it, run it, ship it.
Everything lives at api.chargeid.in/docs — the spec, a live reference and a ready-to-run collection. Go from first read to first call without leaving the page.
OpenAPI spec
One source-of-truth OpenAPI description you can generate a typed client from, in any language. Import it into your tools and go.
Live API reference
Every endpoint, field and example documented and browsable, with real request and response shapes kept in sync with the API.
Ready-to-run collection
Import the collection, drop in a test key and make your first call in minutes — no boilerplate to write first.
Build on India’s charging network.
Get a key, read the docs and route your first live session. We’ll help you scope the integration on a quick call.