Appearance
Errors
Errors use standard HTTP status codes and a JSON body:
json
{
"statusCode": 404,
"message": "Vehicle not found",
"timestamp": "2026-10-23T12:00:00.000Z"
}Partner-specific errors also carry a machine-readable code:
json
{
"statusCode": 401,
"code": "PARTNER_TOKEN_EXPIRED",
"message": "Access token expired",
"timestamp": "2026-10-23T12:00:00.000Z"
}Status codes
| Status | code | What to do |
|---|---|---|
400 | none | A parameter is missing or invalid, or a date range is too long. message says which. Fix the request. |
400 | PARTNER_INVALID_GRANT | /authorize was called without an ID or secret. |
401 | PARTNER_TOKEN_EXPIRED | Get a new token and retry. |
401 | PARTNER_UNAUTHORIZED | Token or credentials are invalid or revoked. Don't retry in a loop. |
403 | PARTNER_FORBIDDEN | The client isn't allowed to use this endpoint. |
404 | none | The vehicle, driver or group in the path or filter doesn't exist in your organisation. |
429 | PARTNER_RATE_LIMITED | Wait Retry-After seconds. See Rate limits. |
503 | PARTNER_SNAPSHOT_UNAVAILABLE | Live data is briefly unavailable. Retry after Retry-After seconds. |
5xx | none | Unexpected server error. Retry with backoff. |
Treat unknown fields in error bodies as optional. More codes may be added.