> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ionage.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Ionage API documentation

> Integration guides and API references for the Ionage EV charging platform

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.

> [card] [Nexus API](https://docs.ionage.in/guides/nexus/overview.md)
>
> Charging stations, chargers, connectors, tariffs, customers, and sessions for
> partner backend integrations. Tenant-scoped.

> [card] [FLO Partner API](https://docs.ionage.in/guides/flo/overview.md)
>
> Fleet operations: drivers, vehicles, remote charging sessions, restrictions, and
> billing. Fleet-scoped.

> [card] [Which API do I need?](https://docs.ionage.in/guides/choosing-an-api.md)
>
> 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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.