Skip to content
Documentation sections

Rate limits

Safecube limits the rate of API requests to protect the platform from receiving more traffic than it can handle, and to share its resources fairly between customers. The limits are subject to change.

Request rate

The current rate limit is 10 requests per 10 seconds per API key.

The limit is counted per API key, not per endpoint: every request sent with the same key counts towards the same allowance.

Exceeding the limit

A request sent above the rate limit is not processed. It receives the status code 429 Too Many Requests.

A 429 response is temporary: retry the request shortly after, once the 10-second window has moved on. To stay below the limit, space requests out on the client side rather than sending them in bursts and retrying the ones that fail.

Congestion API credits

The Congestion API adds a credit quota on top of the rate limit. Its two refusals are distinct:

  • Credit quota reached — the request is answered with 403 Forbidden, blocked before processing, and consumes no credit. Top up the credits or wait for the next period.
  • Too many requests in a short window — the request is answered with 429 Too Many Requests, as on every other Safecube API.

Tracking many containers

Polling the Container Tracking API for every container is the fastest way to reach the rate limit. For high volumes, the Webhooks API reverses the flow: you add your shipments to your tracking list once, and Safecube sends an event to your endpoint whenever new tracking data is available, without any request on your side. The Synchronous and asynchronous tracking page compares both approaches.