Skip to main content
Rate limits depend on your plan. See Pricing for plan details, or 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.
HeaderDescription
RateLimit-Org-Second-LimitMaximum requests allowed per second
RateLimit-Org-Second-RemainingRequests remaining in the current second
RateLimit-Org-Second-ResetSeconds until the per-second limit resets
RateLimit-Org-Day-LimitMaximum requests allowed per day
RateLimit-Org-Day-RemainingRequests remaining today
RateLimit-Org-Day-ResetSeconds until the daily limit resets
RateLimit-Org-Month-LimitMaximum requests allowed per month
RateLimit-Org-Month-RemainingRequests remaining this month
RateLimit-Org-Month-ResetSeconds until the monthly limit resets
RateLimit-Org-TierYour organization’s plan tier name

​
When you hit the limit

The API returns a 429 Too Many Requests response: 
{
  "errors": [
    {
      "title": "Too many requests",
      "detail": "Your request had been throttled"
    }
  ]
}

​
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, fewer calls