Skip to main content
Ionage publishes two public APIs. They serve different integrations, use different credentials, and are versioned independently — pick the one that matches what you are building.

Nexus API

Charging stations, chargers, connectors, tariffs, customers, and sessions for partner backend integrations. Tenant-scoped.

FLO Partner API

Fleet operations: drivers, vehicles, remote charging sessions, restrictions, and billing. Fleet-scoped.

Which API do I need?

A comparison of scope, credentials, and conventions.

Common ground

Both are designed for server-to-server use. Credentials identify an organisation rather than an end user, so they belong on your backend and should never ship inside a mobile or browser application. Beyond that the APIs differ in their conventions — authentication header, ID format, pagination envelope, error reporting, and money representation are all different. Each suite’s guides document its own rules; do not assume behaviour carries across.