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.
.png?fit=max&auto=format&n=Q9Mj_7gZzDeQpRZZ&q=85&s=81619203ea2696cfd7251205cfbc5afc)