How It Works
Rate limiting uses a fixed one-minute window tracked per API key, aligned to UTC epoch boundaries. When the window rolls, the counter resets.
- Per-minute limit - Maximum requests in the current 60-second 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.Prefer Webhooks
Subscribe to content webhooks instead of polling — event-driven sync uses far fewer API calls.
Default Limits
Per-minute limits are configured per site in the Admin Tool and applied when new API keys are created in Dealership Manager.
