Rate limits

Each API key may make 600 requests per minute on average, with bursts of up to 100 requests at once. Limits are per key, so one busy integration doesn’t slow down another. If you need more, contact us.

Every response tells you where you stand, using the IETF RateLimit headers:

RateLimit-Policy: "default";q=600;w=60
RateLimit: "default";r=97;t=1

• q=600;w=60: 600 requests per 60 seconds.
• r: requests you can make right now.
• t: seconds until you are back to a full allowance.

Over the limit, you get 429 rate_limited with a Retry-After header in seconds. Wait that long, then continue.

Staying under the limit

• Use batch endpoints: one POST /v1/fuel_logs/batch with 100 logs costs one request, not 100.
• Use limit=100 when paging, and updated_since instead of full re-reads.
• Use POST /v1/vehicle_positions, which takes up to 1,000 positions per request.
• Spread scheduled jobs out instead of starting them all on the hour.