#Rate Limits
By default a key can make about:
| Requests | Limit |
|---|---|
GET | 20 per minute |
POST | 10 per minute |
All requests from one IP address, across all keys, are also limited to about 60 GET and 30 POST per minute. If your server uses several keys, plan for the shared IP limit as well as each key's limit.
Repeated requests with a missing or invalid key from one IP address are answered 429 partner_rate_limited instead of 401 missing_api_key or 401 invalid_api_key. Fix the key before retrying.
Treat the numbers as a ceiling, not a guaranteed quota. If you need more, ask your BetterTickets contact.
#When you hit the limit
You get 429 partner_rate_limited with a Retry-After header (in seconds) and the same value in the body:
HTTP/1.1 429 Too Many Requests
Retry-After: 42
Content-Type: application/json
{
"error": "partner_rate_limited",
"message": "Too many Partner API requests. Slow down and retry after Retry-After seconds.",
"retry_after_seconds": 42
}Wait at least Retry-After seconds before the next request with that key, or from that IP address.
#Staying under the limit
- Cache event data. Events and ticket types change rarely. Refresh them every few minutes, not on every page view.
- Check availability only when it matters, for example right before a sale, rather than polling every ticket type.
- Batch list writes.
POST /lists/{id}/rowstakes up to 500 rows per call; one call with 500 rows counts as one request. - Serialize retries. Do not retry several requests in parallel after a
429. - Pace retries of
503 auth_unavailable. WaitRetry-Afterseconds between attempts; retrying faster gets429 partner_rate_limited.
async function call(url, init = {}) {
for (let attempt = 0; attempt < 5; attempt++) {
const res = await fetch(url, init);
if (res.status !== 429) return res;
const wait = Number(res.headers.get('Retry-After') || 1);
await new Promise((r) => setTimeout(r, wait * 1000));
}
throw new Error('Still rate limited after 5 attempts');
}