> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fleeticc.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Error codes

> Common Partner API errors and what they mean

Errors look like this:

```json theme={null}
{
  "code": "401",
  "message": "Invalid partner signature.",
  "data": null,
  "error": "PARTNER_AUTH_INVALID"
}
```

| `error` | HTTP | Meaning |
| - | - | - |
| `PARTNER_AUTH_REQUIRED` | 401 | Missing auth headers |
| `PARTNER_AUTH_TIMESTAMP_SKEW` | 401 | Clock too far from server time |
| `PARTNER_AUTH_INVALID` | 401 | Bad key or bad signature |
| `PARTNER_EXTERNAL_API_DISABLED` | 403 | Partner API not enabled for this account |
| `PARTNER_QUERY_INVALID` | 400 | History needs `from`+`to`, or `at` |
| `VEHICLE_NOT_FOUND` | 404 | Vehicle not on your account |
| `TRACK_IMEIS_INVALID` | 400 | Bad or empty IMEI list |
| `DEVICE_NOT_CONNECTED` | 404 | No GPS history available for that device |
| `VEHICLE_SUBSCRIPTION_EXPIRED` | 403 | Vehicle subscription is not active |
| `TOO_MANY_REQUESTS` | 429 | Rate limit hit |
| `INTERNAL_SERVER_ERROR` | 500 | Unexpected server problem |

If something fails repeatedly, contact [info@fleeticc.com](mailto:info@fleeticc.com) with the time, endpoint, and `error` value.


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