Limits and errors
Limits
Section titled “Limits”| Limit | Value | Answer |
|---|---|---|
| Requests per key | 10 a second, bursts of 20 | 429 with Retry-After in seconds |
| Requests per key per day (UTC) | 100,000 | 429 with Retry-After until midnight UTC |
| Failed key checks per client address | 1 a second, bursts of 20 | 429 with Retry-After: 60 |
| Time per request | 30 seconds | 500 |
Your requests per day, per key, are on the API keys page.
Errors
Section titled “Errors”Errors are RFC 9457 problem JSON:
{ "status": 401, "title": "Unauthorized", "detail": "…" }| Status | When |
|---|---|
401 |
The key is missing, malformed, unknown or revoked. |
404 |
No job with that id. |
405 |
Any method other than GET. |
409 |
A since the changes feed never handed out. |
422 |
An unknown, repeated, empty or invalid parameter. The answer names it. |
429 |
Too many requests, or too many bad keys from your address. Wait for Retry-After. |
500 |
Something went wrong on our side, or the request ran past 30 seconds. |
503 |
Backspin is briefly busy. Retry after Retry-After seconds. |
Responses carry Cache-Control: no-store.