Rate Limits
The ByCloud API implements rate limiting to ensure fair usage and protect the service from abuse.
Default Limits
The following rate limits apply to all API endpoints:
| Tier | Requests/Minute | Requests/Hour |
|---|---|---|
| Standard | 60 | 1,000 |
| Professional | 300 | 5,000 |
| Enterprise | 1,000 | 20,000 |
Rate Limit Headers
Every API response includes headers to help you track your rate limit status:
X-RateLimit-Limit - Maximum requests allowed per window
X-RateLimit-Remaining - Requests remaining in current window
X-RateLimit-Reset - Unix timestamp when the window resets
Handling Rate Limits
When you exceed the rate limit, the API returns a 429 Too Many Requests response with a Retry-After header indicating how long to wait before retrying.
HTTP/1.1 429 Too Many Requests
Content-Type: application/json
Retry-After: 30
X-RateLimit-Limit: 60
X-RateLimit-Remaining: 0
X-RateLimit-Reset: 1705320000
{
"error": {
"code": 429,
"message": "Rate limit exceeded",
"details": "Please wait 30 seconds before retrying"
}
}Best Practices
• Implement exponential backoff when retrying failed requests
• Cache responses when possible to reduce API calls
• Use webhooks instead of polling for real-time updates
• Monitor your rate limit headers to avoid hitting limits
• Contact support if you need higher rate limits