Rate Limits
The Partner API enforces rate limits to ensure fair usage and system stability.
Rate Limit Values
| Limit Type | Limit | Window |
|---|---|---|
| Per API Token | 300 requests | 1 minute |
| Per IP Address | 1000 requests | 1 minute |
The per-token limit applies to authenticated requests. The per-IP limit provides additional protection against unauthenticated abuse.
Rate Limit Headers
Every response includes headers showing your current rate limit status:
| Header | Description |
|---|---|
X-RateLimit-Limit |
Maximum requests allowed per window |
X-RateLimit-Remaining |
Requests remaining in current window |
X-RateLimit-Used |
Requests used in current window |
Example Response Headers
X-RateLimit-Limit: 300
X-RateLimit-Remaining: 297
X-RateLimit-Used: 3
Exceeding the Rate Limit
When you exceed the rate limit, the API returns a 429 Too Many Requests response with a Retry-After header indicating how many seconds to wait:
HTTP/1.1 429 Too Many Requests
Retry-After: 45
{
"error": {
"code": "RATE_LIMITED",
"message": "Too many requests. Please try again later."
}
}
Best Practices
To stay within rate limits:
- Cache responses when possible to reduce repeated requests
- Use pagination efficiently by requesting appropriate page sizes
- Implement exponential backoff when retrying after rate limit errors
- Monitor your usage using the rate limit headers
- Batch operations where the API supports it
Need Higher Limits?
If your integration requires higher rate limits, contact your Roundtable account manager to discuss your use case.