Developers / Rate limits
Two independent budgets: how fast you may call, and how much you may call in a month.
Rate limit — requests per minute. Exceed it and you get 429. Clears in 60 seconds.
Credits — your monthly allowance. Exhaust it and you get 402. Retrying will never clear it; it resets on the 1st of each calendar month at 00:00 UTC.
Every billed response carries your credit position in its headers, so your own request log shows where you stand without an extra call. They are the same numbers GET /v1/usage returns, and that call is free.
| Header | What it carries |
|---|---|
X-Credits-Cost | What this call cost. 0 on a 304 Not Modified and on the free endpoints. |
X-Credits-UsedX-Credits-LimitX-Credits-Remaining | Credits used this calendar month, your monthly allowance, and what is left of it. Limit reads unlimited on a plan without one; Remaining reads 0 once you are past the allowance, even while overage is carrying you. |
X-Credits-Pct-UsedX-Credits-Warning | Used as a percentage of the allowance, to one decimal. Warning: approaching-limit appears once you are close, together with the four X-Upgrade-* headers below. |
X-Upgrade-PlanX-Upgrade-CreditsX-Upgrade-Price-AUDX-Upgrade-Url | The tier that would cover your measured usage: its key, allowance, monthly price in AUD and a link to it. Also on every 402 (with Link: rel="payment") and on a plan-gate 403. |
X-Credits-Key-UsedX-Credits-Key-CapX-Credits-Key-Remaining | Only on a team key that has its own monthly cap: that key's count, cap and headroom. The X-Credits-* headers above are the shared pool. |
X-Credits-OverageX-Credits-Overage-Ceiling | Only while overage is carrying you past the allowance: how far past you are, and the ceiling at which you will be refused. |
X-Billing-StatusX-Billing-Next-AttemptX-Billing-Update-Url | Only while an invoice on the key is unpaid: past_due, when the card is retried next, and where to update it. |
X-RateLimit-LimitX-RateLimit-Remaining | The per-minute window, and Retry-After on a 429. |
X-Horizon-Hours | On /v1/racing/events and /v1/racing/best-odds: how far ahead your plan reaches. |
| Plan | Price | Requests / minute | Credits / month |
|---|---|---|---|
| Free | $0 | 30 |
1,500 |
| Hobby | $9/mo | 60 |
7,500 |
| Standard | $29/mo | 200 |
75,000 |
| Plus | $49/mo | 500 |
140,000 |
| Business | $99/mo | 750 |
300,000 |
| Platform | $199/mo | 1000 |
1.5M |
| Scale | $249/mo | 2000 |
5M |
A 60-second sliding window per API key — not a fixed clock minute. Sixty requests at 10:00:59 and sixty more at 10:01:01 will trip the limit on a 60/min plan, because the window looks back 60 seconds from now, not to the top of the minute.
Sandbox endpoints under /v1/demo/ are limited separately, by IP, at 30 requests/minute — they need no key, so there is no key to meter.
HTTP/1.1 429 Too Many Requests
Retry-After: 60
X-RateLimit-Limit: 30
X-RateLimit-Remaining: 0
Content-Type: application/problem+json
Retry-After is in seconds. Honour it rather than retrying immediately — a tight retry loop keeps the window full and you stay limited.
/v1/racing/next-to-go returning many races costs 2 credits or 3 credits or 4 credits; fetching each race separately costs far more of both budgets./v1/racing/next-to-go carries an ETag; repeat the call with If-None-Match and an unchanged board is answered 304 Not Modified for 0 credits and no body (it still counts as one request in the per-minute window). The official Python and Node clients do this for you by default./v1/sports changes rarely.quality object with age_seconds — if the price you hold is as fresh as the one you would fetch, skip the call.If your workload genuinely needs more throughput than Scale's 2000/min, get in touch rather than sharding across keys — we would rather size a plan to the use case.
Errors · Freshness · Pricing & credits · API reference · Live status