Skip to main content
Every request must include an x-api-key header.

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

Cross-fleet access returns 404, not 403 — the API does not confirm that a resource exists in a fleet you cannot see.
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.