Skip to main content
Use this page to prevent limit-related interruptions in your API integrations.

Current API rate limits

  • Up to 3,600 daily requests
Use 3,600 requests/day as your planning baseline unless support confirms a different account-specific limit.

What this means in daily operations

  • 3,600/day is about 150 requests/hour on average.
  • 3,600/day is about 2.5 requests/minute on average.
  • Short bursts can still happen, but sustained traffic should stay under budget.
  • Contact support if your normal traffic now exceeds your current baseline.

Plan your request budget

1

Estimate your normal traffic

Calculate how many API calls one user journey triggers, then multiply by expected daily sessions.
2

Add safety headroom

Reserve part of the budget for retries, support checks, and traffic spikes.
3

Set soft alerts

Add internal alerts around 70%, 85%, and 95% of daily capacity.
4

Reduce avoidable calls

Cache stable responses and remove duplicate polling.
5

Review usage every week

Compare forecast vs real usage and adjust before limits become incidents.

If you are close to today’s limit

  • Pause non-critical background jobs.
  • Increase cache duration for low-change data.
  • Investigate duplicate or noisy request sources.
  • Keep only customer-critical API calls active.
  • Contact support if your normal traffic now exceeds your current baseline.
Do not wait for a hard-limit event in production. Use soft alerts and early traffic controls.