Operators with engineering teams kept asking the same question: can we get session data into our own systems without waiting for a report to be built. The answer is now yes, and it is the same interface the console uses rather than a reduced export surface bolted on beside it.
What is available
- Stations, connectors, sessions, drivers, tariffs, partners and settlements — read and, where it makes sense, write.
- Remote commands: start, stop, reset, unlock, set availability and charging profiles.
- Cursor pagination and filtering on every collection, so a year of sessions is a loop rather than a timeout.
- Idempotency keys on every write, so a retried request cannot double-apply.
Webhooks
Session started, session completed, station status changed, station offline, settlement generated. Each delivered as a signed POST with retries and exponential backoff.
Sandbox
A sandbox tenant with simulated chargers is available on request. It runs the same API with seeded stations and sessions, so an integration can be built and tested before any hardware is commissioned.
releaseAPIintegration