Access & rate limits
| Sign-up | None |
| Rate limit | 1000 requests per minute per IP |
| Edge burst limit | 170 requests per 10 seconds per IP, then a 10-second block. See the edge burst limit |
| Over the rate limit | 429, code rate_limited, header Retry-After (seconds) |
| Browser cache | Cache-Control: public, max-age=300; /v1/dump and /v1/index: max-age=3600 |
| Edge cache | 10 minutes |
ETag |
"<dataset_version>". Send it in If-None-Match for a 304. See Caching & conditional requests |
| CORS | Any origin, GET only, no credentials. See CORS |
/health |
Not rate limited |
Retry-After
Section titled “Retry-After”After 1000 requests in a minute from one IP, the rest of that minute’s
requests get a 429:
curl -i https://truefloat.app/api/v1/items/7/44HTTP/2 429content-type: application/jsonretry-after: 60access-control-allow-origin: *access-control-expose-headers: ETag, Retry-After
{"dataset_version": "e9c25a6", "error": {"code": "rate_limited", "message": "Too many requests"}}Wait Retry-After seconds before retrying. If a 429 has no Retry-After
or no JSON body, wait 60 seconds.
The edge burst limit
Section titled “The edge burst limit”Cloudflare, in front of the API, allows at most 170 requests in 10 seconds from one IP, then blocks that IP for 10 seconds.
The block response comes from Cloudflare and has no CORS headers. Outside a
browser it is an ordinary 429. In a browser on another origin, fetch()
rejects with a network error (a TypeError) instead.
Treat that error like a 429: wait 10 seconds and retry. The
quickstart helper does this.
- Every response, including errors,
429and304, carriesAccess-Control-Allow-Origin: *andAccess-Control-Expose-Headers: ETag, Retry-After, with or without anOriginheader. Responses don’t vary onOrigin. GETonly. Don’t send credentials (credentials: 'include').- A preflight (
OPTIONS) allowsGETwith anIf-None-Matchheader.