← THE CHARTSPOD LEDGEROPEN TERMINAL →
API · RATE LIMITS

DEX API Rate Limits: Separate Pair Requests From Profile Requests

DEX Screener's API documents different rate limits for different endpoint groups. Mixing them in one loop hits the tighter limit first.

By ChartsPod Editorial Team · Reviewed by ChartsPod Research
Published · Updated · 5 min read

Short answer

DEX Screener's API reference lists 60 requests per minute for several profile, takeover, ads, metas and boosts endpoints, and states separate limits for pair and token endpoints. Design your client with a separate rate limiter per endpoint group, schedule profile calls less often than pair calls, cache responses that change slowly (profiles, metadata), and back off on errors rather than retrying immediately. Check the current limits in the reference before deploying.

Endpoint groups

GroupExamplesChange frequencySuggested polling
Profiles / metadatatoken-profiles, community-takeoversSlowMinutes to hours; cache
Boosts / ads / metastoken-boosts, ads, metasMediumMinutes
Pairs / tokenspairs, token-pairs, tokensFastAs limits allow
One limiter vs per-group limitersOne limiter vs per-group limiters. Left, One shared limiter: Slow endpoints throttle fast ones; Hard to reason about; Wastes budget. Right, Per-group limiters: Each group within its limit; Priorities explicit; Caches reduce calls.ONE SHARED LIMITERSlow endpoints throttle fast onesHard to reason aboutWastes budgetPER-GROUP LIMITERSEach group within its limitPriorities explicitCaches reduce calls
Separate budgets avoid needless throttling. Original ChartsPod editorial graphic.

Put DEX API Rate Limits next to price, flow and positioning in one workspace.

Open a ChartsPod workspace

Client design

Rate-limited clientRate-limited client. Steps: 1. Classify call — Endpoint group; 2. Check limiter — Tokens available?; 3. Use cache — If fresh enough; 4. Call API — Log status; 5. Back off — On 429/errors1Classify callEndpoint group2Check limiterTokens available?3Use cacheIf fresh enough4Call APILog status5Back offOn 429/errors
Backoff prevents bans and wasted calls. Original ChartsPod editorial graphic.
Illustrative calls per minute after caching profilesIllustrative calls per minute after caching profiles: Without cache 140 calls; With 10-min profile cache 62 calls.ILLUSTRATIVE CALLS PER MINUTE AFTER CACHING PROFILESWithout cache140 callsWith 10-min profile cache62 calls
Caching slow-changing data frees budget. Original ChartsPod editorial graphic.

Mistakes

Polling profiles as often as prices; retrying instantly on 429 responses; batching too many token addresses in one call beyond documented limits. Each leads to throttling or incomplete data.

Example: budget planning

Illustrative: a monitor tracks 200 tokens. Pair data is needed every minute for 20 high-priority tokens and every 15 minutes for the rest; profiles are refreshed hourly. Grouping token addresses where the endpoint allows multiple addresses per call, and caching profiles, keeps each endpoint group within its published limit with headroom for retries.

Conclusion

Related: DEX Screener API vs GeckoTerminal API: Pair Snapshots or Candle History?, DEX Screener API: Find Token Pools by Chain and Contract Address.

Give each DEX Screener endpoint group its own limiter and cache slow-changing data.

Review DEX API Rate Limits with bar replay before using it live.

Open ChartsPod replay

Questions readers ask

What are DEX Screener's API rate limits?

Several endpoints list 60 requests per minute; check the reference for each.

Should I cache responses?

Yes, especially profiles and metadata.

What should I do on a 429?

Back off with increasing delays.

Sources and methodology

API behaviour comes from DEX Screener's API reference, CoinGecko's onchain API documentation and Binance's USD-M market data documentation as read on 17 October 2026. Code-level details are described conceptually; check current endpoint versions before building. Examples use illustrative values.

  1. DEX Screener: API reference — token and pair endpoints, nullable fields, rate limits.

This article explains research tools and workflows. It is not financial advice, does not recommend buying or selling any asset and does not predict prices. Crypto derivatives carry a risk of rapid and total loss of margin.

CHARTSPOD EDITORIAL EDITION · RESEARCH AND EDUCATION ONLY · NOT FINANCIAL ADVICE.