How It Works
Rate limiting uses a sliding window algorithm tracked per API key. The window continuously rolls forward — it is not reset at fixed intervals.
- Per-minute limit - Maximum requests in any rolling 60-second window
- Per-day limit - Maximum requests in any rolling 24-hour window
429 Too Many Requests.
Rate Limit Headers
Every response includes these headers so you can proactively monitor usage without making extra API calls.
Handling Rate Limits
When you exceed the limit, you’ll receive:Retry-After header with the number of seconds to wait.
Best Practices
Respect Retry-After
Always wait the number of seconds specified in the
Retry-After header before retrying.Exponential Backoff
If you continue hitting limits, implement exponential backoff with jitter.
Use Batch Endpoints
For bulk operations, use batch endpoints (
/ideaclouds/batch, /content/batch) to reduce request count.Monitor Headers
Track
X-RateLimit-Remaining and throttle proactively before hitting the limit.Default Limits
Rate limits are configured per API key when creating the key in the Dealership Manager.
