Rate limits

Limits are counted per API client in fixed one-minute windows.

Endpoints	Limit
All /fleet/* data endpoints, combined	600 calls per minute per client
GET /fleet/driving-times	30 per minute per client, and 60 per minute per organisation, inside the 600
POST /authorize	10 per minute per client, 20 per minute per IP address, and 600 per minute across all clients
GET /vehicles (v1 fleet snapshot)	120 per minute per client
GET /ping	60 per minute per client

When you go over a limit you get:

HTTP/1.1 429 Too Many Requests
Retry-After: 60

{
  "statusCode": 429,
  "code": "PARTNER_RATE_LIMITED",
  "message": "Too many requests",
  "timestamp": "2026-10-23T12:00:30.000Z"
}

Wait at least Retry-After seconds before trying again.

Polling advice

• Live positions are refreshed about every 12 seconds on our side, so polling /fleet/positions or /vehicles more often than every 15–30 seconds gains nothing. include=activityToday on /vehicles is cached for the same 12 seconds.
• Reference data (vehicles, groups, drivers, geofences, points of interest) changes rarely. Refresh it every few minutes or hours, not on every position poll.
• History (daily summary, trips, alerts, driver scores) for a closed day doesn't change. Fetch it once and store it. Driving times is the heaviest of these and is capped lower than the shared 600.