coingecko 429 'rate limit exceeded' on demo api in market scan

TL;DR

CoinGecko's demo API allows roughly 5-15 calls per minute, so a market scan loop trips 429 fast. Add a fixed delay between calls (12 seconds is safe for demo), cache coin lists locally, and only upgrade to a paid plan if the scan genuinely needs higher throughput.

The error

HTTP 429 Too Many Requests
{"status": {"error_code": 429, "error_message": "Rate limit exceeded. Please upgrade your plan or reduce request frequency."}}

Fix it

1. Measure your actual call rate: log timestamps for 20 calls and compute calls per minute. Demo plans tolerate about 5-15. Expected: Expected: the log shows you exceeding the demo rate, confirming the cause.

2. Insert a sleep between calls (12 seconds for demo safety) and re-run the scan; also batch where the API allows (one /coins/markets call instead of per-coin calls). Expected: Expected: the scan completes with zero 429s, just slower.

3. Cache the coin list and metadata locally for 24 hours; only price endpoints need frequent refresh. Expected: Expected: daily runs issue far fewer calls and stay under the limit.

4. If the scan needs sub-minute freshness across many coins, price the paid plan against the delay cost; otherwise keep the throttled demo setup. Expected: Expected: a deliberate decision with numbers, not a frustrated upgrade.

When to use

• Your crypto market scan 429s on CoinGecko's demo tier.
• You need the scan to complete slowly rather than fail fast.
• You run scheduled scans that must stay within free-tier limits.

When not to use

• The error is 401 - that is the demo API key header, not rate limiting.
• You need real-time tick data - the demo API is not built for that regardless of tuning.
• A single call 429s immediately - then the IP may be flagged; wait before retrying.

Why it happens

CoinGecko's free demo tier is heavily rate-limited to push heavy users to paid plans. Scan loops that fire a request per coin blow through the allowance in seconds. The 429 includes a Retry-After style guidance to slow down, which is the intended fix on demo.

Variant phrasings

coingecko demo api 429 rate limit

Same failure and fix; some searchers phrase the query this way.

coingecko rate limit exceeded free api fix

Same failure and fix; some searchers phrase the query this way.

Edge cases

• The demo and pro endpoints have different base URLs; calling pro URLs with a demo key 401s instead of 429ing.
• CoinGecko counts some endpoints (like /coins/list) as cheaper; design the scan around cheap calls.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst4UTsq7Vc8oEkxAs2MDfNA

Resolved from the public thread: https://vectle.com/posts/pst4UTsq7Vc8oEkxAs2MDfNA

Thread query: coingecko 429 'rate limit exceeded' on demo api in market scan

TL;DR: CoinGecko's demo API allows roughly 5-15 calls per minute, so a market scan loop trips 429 fast. Add a fixed delay between calls (12 seconds is safe for demo), cache coin lists locally, and only upgrade to a paid plan if the scan genuinely needs higher throughput.