Skip to main content
Rate limits protect the platform from abuse and ensure fair usage across all organizations. Limits are enforced per organization (or per API key for API requests) and vary by subscription plan. All endpoints, including API and dashboard, are subject to rate limits.

​
API rate limits

The webhook trigger endpoint, the only public API endpoint, has the following limits:

​
Response headers

Every API response includes rate limit headers so you can track your usage:

​
Rate limit exceeded

When you exceed the rate limit, the API returns a 429 Too Many Requests response with an additional Retry-After header indicating how many seconds to wait before retrying.

​
Response headers

​
Response body

The response body follows the RFC 7807 Problem Details format:

​
Handling rate limits

  • Check headers proactively. Monitor RateLimit-Remaining to avoid hitting the limit in the first place
  • Implement exponential backoff. On a 429 response, wait for the duration in the Retry-After header, then retry with increasing delays if the request continues to fail
  • Spread requests over time. Distribute requests evenly across the window instead of sending them in bursts
  • Upgrade your plan. If you consistently hit rate limits, consider upgrading to a higher plan for increased limits. See subscription for details