- Home
- Developers
Developers
Build on the platform your console runs on.
One API for your backend and your own driver app, with access set per organisation and nothing granted that you didn’t enable.
Two kinds of credentials
Keys for servers. Tokens for drivers.
An API key never goes inside a mobile app, where anyone could extract it. Your backend uses keys; each driver in your app gets a short-lived token of their own.
For your backend and tools
Locations, charger status, sessions, tariffs and invoices. Each key carries its own scopes and rate tier and can be revoked at any time.
For your own driver app
A ChargeIT-hosted login in your branding. Each token is limited to that one driver: their sessions, their tags, their payments.
The driver API
Everything a driver app needs.
Built on the same driver accounts the ChargeIT app uses, so you don’t build a second user system. Drivers’ personal and payment data stay on ChargeIT’s side.
Find chargers
- Map search
- Live availability
- Prices
Charge
- Start and stop by QR or connector
- Live kWh, power and cost
Account
- Profile
- RFID tags
- Payment methods
- History and receipts
Events
- Session updates by webhook
- Or push, sent for you
Driver login
No backend needed to sign drivers in.
Who gets the panel
Switched on per organisation.
| Organisation | Full console | Developers panel | Typical use |
|---|---|---|---|
| Hybrid | Yes | Yes | White-label operator with its own driver app |
| API-only | — | Yes | A product team building everything itself |
| Everyone else | Yes | — | Operators using the console and the ChargeIT app |
Tell us what you’re building.
We’ll enable the scopes you need and set up your organisation.
Request API access