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

# Authentication

> Every FLO Partner API request carries a fleet-scoped API key

Every request must include an `x-api-key` header.

```bash theme={null}
curl https://api.ionage.in/public/fleets/v1/stations \
  -H "x-api-key: your-api-key"
```

## Fleet scoping

The API key identifies **exactly one fleet**. There is no fleet ID in any path or
body — the key determines which fleet's drivers, vehicles, sessions, and billing you
can see and modify.

A consequence worth designing around: serving more than one fleet means holding more
than one key and selecting the right one per request. Keys cannot be combined, and a
response never spans fleets.

## Failure modes

| Condition | Response |
| - | - |
| Header missing | `401 Unauthorized` |
| Key not recognised | `401 Unauthorized` |
| Key valid but resource belongs to another fleet | `404 Not Found` |

> [!NOTE]
>
> Cross-fleet access returns `404`, not `403` — the API does not confirm that a
> resource exists in a fleet you cannot see.

> [!WARNING]
>
> Because the key alone grants full access to a fleet's data, it must stay on your
> backend. Never ship it in a driver app or a browser client.


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