Getting started

Rate limits

600 requests per hour per key and the headers that track it.

Each key may make 600 requests per hour. The window is the clock hour in UTC, so it resets at :00. Limits are per key, not per account — use several keys for several apps.

Headers on every response

x-ratelimit-limit

Requests allowed per hour (600).

x-ratelimit-remaining

Requests left in the current hour.

x-ratelimit-reset

Seconds until the window resets.

retry-after

Only on 429: seconds to wait.

x-request-id

Quote it when reporting a problem.

Over the limit

HTTP/1.1 429 Too Many Requests
retry-after: 1260

{ "error": { "code": "quota_exceeded", "message": "…", "status": 429 } }

Burst limit

On top of the hourly quota, each endpoint has a short per-minute budget per key (45 requests per minute on heavy endpoints such as /v1/coins and /v1/prices, 120 on the rest). Exceeding it returns 429 rate_limited with a retry-after header; it does not consume your hourly quota.

Staying under it

Use /v1/prices?ids= for polling (one call covers many assets), request list endpoints with the limit you actually render, and cache for at least the refresh interval shown on each reference page. A dashboard refreshing ten assets every 10 seconds uses 360 calls per hour.

Need more for a public, attributed project? Email [email protected] with what you are building.

← Authentication Errors →