Rate Limiting
API requests are rate-limited to ensure fair usage and platform stability.
Limits
| Endpoint Group | Limit |
|---|---|
| General API endpoints | To be confirmed — contact support for details |
Rate limits apply per workspace.
Rate Limit Headers
Each response includes headers that indicate your current rate limit status:
| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum number of requests allowed per window |
X-RateLimit-Remaining | Number of requests remaining in the current window |
Retry-After | Seconds to wait before retrying (only on 429 responses) |
Exceeding the Limit
When you exceed the rate limit, the API returns:
json
{
"message": "Too Many Attempts."
}Status: 429 Too Many Requests
Best Practices
- Implement exponential backoff when you receive a 429 response
- Use the
Retry-Afterheader value as your delay time - Batch requests when possible to reduce total API calls
- Cache responses for data that doesn't change frequently
- Monitor your rate limit headers to stay within limits
Increasing Limits
If you need higher rate limits for your integration, contact support with your expected usage volume.