Rate Limiting
Understand request limits and how throttling is enforced.
SMARTe APIs enforce rate limits to ensure platform stability, fair usage, and consistent performance across all clients.
Rate limits are applied per organization and evaluated across all API requests made using that organization’s credentials.
How Rate Limiting Works
- Each request is evaluated against configured limits before enrichment processing begins.
- Requests that exceed the allowed threshold are rejected immediately.
- Rate-limited requests do not consume credits.
Rate Limit Response
When a rate limit is exceeded, the API returns:
- HTTP Status:
429 Too Many Requests - Error Code:
rate_limit_exceeded
{
"error": {
"code": "rate_limit_exceeded",
"message": "Too many requests. Please try again after some time.",
"status": 429
}
}Retry Guidance
Treat 429 responses as transient failures. Recommended approach:
- Use exponential backoff
- Avoid immediate retries
- Distribute high-volume requests over time
Rate limits vary by contract. If your integration requires higher throughput, contact SMARTe Support with expected request volume and usage patterns.
Updated 29 days ago