Skip to main content
Rate limits depend on your plan. Visit the Dashboard to view your current limits and usage.

​
Monitoring usage

Every API response includes rate limit headers with your current limits and remaining quota. For a full usage breakdown, visit the Dashboard and click Open Analytics Dashboard.

​
When you hit the limit

The API returns a 429 Too Many Requests response:

​
Handling rate limits

Use the RateLimit-Org-Second-Reset header to wait the exact time needed before retrying a 429 response. If your day or month quota is exhausted, retrying won’t help. Check RateLimit-Org-Day-Remaining and RateLimit-Org-Month-Remaining first.

​
Tips to stay under the limit

  • Use webhooks instead of polling - transaction subscriptions give you real-time updates without repeated requests
  • Cache responses where data doesn’t change frequently (e.g., chain lists, token metadata)
  • Use filters and pagination to fetch only the data you need. Smaller requests mean fewer calls

​
Advanced endpoints

Requests to wallet positions with filter[positions]=no_filter or only_complex, wallet balance charts, and PnL count toward an advanced sublimit of 25% of your plan’s monthly quota. Advanced requests are not eligible for overages. When the sublimit is reached, these endpoints return 429 while other endpoints keep working. Track usage in the Dashboard.

​
Overages

Paid plans can enable overages in the Dashboard. Usage beyond your monthly quota is billed instead of blocked, up to a cap you set.

​
Per-key limits

You can set a custom RPS or monthly cap on individual API keys in the Dashboard, for example to isolate a development key.

​
Per-wallet throttling

Repeated requests for the same wallet address in a short window can return 429 even when your organization limits are not reached. Cache responses per wallet or use webhooks for real-time updates.