API rate limits
The webhook trigger endpoint, the only public API endpoint, has the following limits:| Plan | Requests per minute |
|---|---|
| Free | 10 |
| Basic | 60 |
| Standard | 300 |
| Premium | 1,000 |
Response headers
Every API response includes rate limit headers so you can track your usage:| Header | Description |
|---|---|
RateLimit-Limit | Total allowed requests in the current window |
RateLimit-Remaining | Requests remaining in the current window |
RateLimit-Reset | Unix timestamp (seconds) when the window resets |
Rate limit exceeded
When you exceed the rate limit, the API returns a429 Too Many Requests response with an additional Retry-After header indicating how many seconds to wait before retrying.
Response headers
| Header | Description |
|---|---|
Retry-After | Seconds until the rate limit window resets |
RateLimit-Limit | Total allowed requests in the current window |
RateLimit-Remaining | 0 |
RateLimit-Reset | Unix timestamp (seconds) when the window resets |
Response body
The response body follows the RFC 7807 Problem Details format:Handling rate limits
- Check headers proactively. Monitor
RateLimit-Remainingto avoid hitting the limit in the first place - Implement exponential backoff. On a
429response, wait for the duration in theRetry-Afterheader, 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