Peer with AthenireCharge
We run both halves of roaming. As a CPO we publish our chargers so your drivers can use them; as an eMSP we send our drivers to yours. One bilateral agreement, one token exchange, and both directions work.
Connection details
The versions URL is the only address you need to keep. Everything else in OCPI is discovered from it.
- OCPI version
- 2.2.1
- Party
- IN*ATH
- Country code
- IN
- Party id
- ATH
- Roles
- CPO, eMSP
- Versions endpoint
- https://csms.athenire.com/ocpi/versions
- Business name
- AthenireCharge — Athenire Pvt. Ltd.
- Technical contact
- roaming@athenire.com
curl https://csms.athenire.com/ocpi/versions \ -H "Authorization: Token <YOUR_TOKEN_A>"
Modules we implement
SENDER means we publish the data; RECEIVER means we accept yours. Getting these the wrong way round is the classic OCPI integration failure, so they are listed explicitly.
| Module | Role | What it does |
|---|---|---|
| Credentials & Versions | BOTH | The registration handshake. Token A starts it; we return Token C. |
| Locations | BOTH | We publish our stations, EVSEs and connectors with live status, and read yours. |
| Tariffs | SENDER | Our prices, so your drivers see the real cost before they plug in. |
| Tokens | BOTH | Push us your driver tokens; we honour whitelist NEVER with a real-time authorize call to you. |
| Commands | BOTH | START_SESSION, STOP_SESSION and UNLOCK_CONNECTOR, answered asynchronously on your response_url. |
| Sessions | BOTH | Live session mirroring while a charge runs, in both directions. |
| CDRs | BOTH | Charge Detail Records for settlement, retried until you accept them. |
Not implemented
Listed so you can plan around it rather than discover it during integration.
- · Hub role — we peer bilaterally; India has no clearing house to sit behind.
- · ChargingProfiles over OCPI — smart charging stays on OCPP, where we hold the socket.
- · The Booking module — reservations are OCPP-side only for now.
How registration works
- 1
Tell us who you are
Send your country code, party id, role and a technical contact. We counter-sign a roaming agreement — this part is commercial, not technical.
- 2
Collect your Token A
We issue a single-use registration token. It authorises exactly one thing: reaching the credentials endpoint. It stops working the moment you complete the handshake.
- 3
POST /credentials
Send us your token and versions URL. We store yours, mint your Token C, and return it. Use Token C on every call from then on.
- 4
You are live
We discover your endpoints automatically from your versions document. Your drivers can charge on our network, and ours on yours.
Credentials are issued by a person, not a form. Anyone who completes the handshake can start charging sessions on our hosts' hardware and owes us for the energy afterwards. That makes roaming a billing relationship, so the token follows the agreement rather than the other way round.
Why peer
Utilisation
When Indian CPOs joined a common roaming layer in 2023, charger utilisation moved from under 10% to over 20%. Idle connectors are the industry's biggest cost.
Compliance
India's 2025 charging guidelines push new public chargers onto open protocols, with larger networks expected to join a roaming arrangement.
One integration
Direct bilateral peering, no clearing-house fee in between. We implement both roles, so a single handshake opens both directions.
Questions before you start? roaming@athenire.com · Back to athenire.com