> ## 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.

# Choosing an API

> How the Nexus and FLO Partner APIs differ

## At a glance

| | Nexus API | FLO Partner API |
| - | - | - |
| **Built for** | Partner backends reading charging infrastructure and driving sessions | Fleet operators managing drivers, vehicles, and fleet charging |
| **Standard** | Ionage-defined | Ionage-defined |
| **Scope** | Tenant | Fleet (one fleet per API key) |
| **Credential** | `X-Tenant-ID` header | `x-api-key` header |
| **Host** | Platform host | Platform host |
| **Errors** | HTTP status | HTTP status, `error.code` envelope |
| **Pagination** | `limit`/`offset`, `links` object, `X-Total-Count` header | `limit`/`offset`, `metadata` object |
| **Money** | Not applicable at the API surface | Integer paise |

## Pick Nexus if

You are a partner backend that needs to read the charging network — stations, chargers,
connectors, and structured tariffs — and start or stop sessions on behalf of customers
you already manage.

## Pick FLO if

You are building fleet tooling: an operations dashboard, a driver app, or a
backend-for-frontend. FLO adds the fleet concepts Nexus does not model — driver
onboarding, a vehicle registry, connector-level charging restrictions, and fleet
billing.

> [!NOTE]
>
> The two APIs are independent. Identifiers are not interchangeable between them, and
> a credential for one will not authenticate against another.


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