Paste this. It works.
Discovery is public, because the map has to draw before anybody signs in. So there is no key to request and no form in front of the first call — the request below runs against production right now.
curl "https://api.athenire.com/v1/stations?lat=17.385&lng=78.4867&radius_km=25&limit=2"[
{
"id": "pk-061bf1",
"name": "Pk",
"latitude": 17.4435,
"longitude": 78.3772,
"available": 1,
"total": 1,
"max_power_kw": 30,
"price_per_kwh": 18.0,
"currency": "INR",
"connector_types": ["CCS2"],
"distance_km": 13.31,
"source": "network",
"price_known": true,
"reliability": null
}
]Two fields worth noticing. source says whether a listing is ours, a roaming partner's, or a public charger we can show but not book — the app draws and starts each differently. price_knownis false when we hold no published tariff, so you can render “price at start” instead of a zero that reads as free.
Two hundred operations, one spec
Generated from the running service, so the documentation cannot drift from the API.
API reference
Searchable, with a request builder on every operation. Rendered by Scalar from our own OpenAPI document.
OpenAPI 3.1
The raw spec. Generate a client in whatever language you are in, rather than reading prose and hoping.
Swagger
The same spec in the interface you may already be used to. ReDoc is at /redoc.
Open standards, including the one we have not finished
A protocol list is only useful if it distinguishes what is running from what is intended.
OCPP 1.6-J and 2.0.1
Point a charge point at our CSMS websocket and it registers itself. Both subprotocols are offered on the handshake, in preference order, and the charger picks.
OCPI 2.2.1, both roles
We run the CPO side and the eMSP side, so we can accept a partner's drivers and send ours out. Party id, versions URL and credentials handshake are on the roaming page.
Beckn / UEI
BAP and BPP against core 1.1.0 and the ev-charging:uei domain, so a charge here is discoverable from any UEI-compliant app rather than only from ours.
ISO 15118
Plug-and-charge identifiers are carried through the session model. The certificate handling that makes it usable end to end is not built yet, and we would rather say so.
A charge point, in your browser
A real OCPP charge point that boots, heartbeats, authorises, streams MeterValues and evaluates smart-charging profiles — all client-side, so you can watch the frames without owning hardware or asking us for anything. Run a fleet of them if you want to see what load looks like.
Open the simulatorPeering as a network instead? Our OCPI details are here.