Rate Limiting

The SuprSync External API enforces per-client rate limits using a token bucket algorithm to ensure fair usage and platform stability.

Default Limits

Limits are configurable per API client. Contact your SuprSync admin if you need higher limits.

How It Works

The token bucket algorithm refills tokens at a steady rate (your per-minute allowance divided over the minute). Each request consumes one token. The burst capacity allows short spikes of traffic above the steady rate.

Rate Limit Response

When you exceed the rate limit, the API responds with HTTP 429:

{
  "error": {
    "code": 429,
    "message": "Rate limit exceeded"
  }
}

Headers

Best Practices

• Respect Retry-After - Wait the indicated number of seconds before sending the next request.
• Implement exponential backoff - On repeated 429s, increase the wait time between retries.
• Cache responses - Store data that doesn't change frequently (locations, job roles) to reduce API calls.
• Batch where possible - Use filtering parameters to retrieve exactly the data you need in fewer requests.