Rate Limiting
To ensure fair usage and protect the stability of the Celenity API, all requests to our API endpoints are subject to rate limiting.
Each account has a rate limit based on the type of account (defaults to 60 Requests per minute).
You can find details of your account plan on the accounts page on your console.
Requests exceeding this limit will receive a 429 Too Many Requests response.
How It Works
Every account has a maximum number of requests per minute (the rate limit).
Each request reduces your available quota.
Quotas reset automatically after a short period (default: 60 seconds).
If your account requires a higher rate limit, please contact support.
Response Headers
Every API response includes helpful headers so you can track your usage:
X-RateLimit-Limit
Maximum number of requests allowed in the current window.
X-RateLimit-Remaining
Number of requests still available before hitting the limit.
X-RateLimit-Burst
Maximum allowed burst capacity (short-term extra requests).
Retry-After
Seconds to wait before retrying if the limit has been exceeded (only on 429).
Example: Normal Response
Example: Rate Limit Exceeded
⚠️ Important: A
429 Too Many Requestsis not an application error. It simply means you have sent too many requests in a short period. Your application should pause and retry after the number of seconds specified in theRetry-Afterheader.
Best Practices
✅ Check the response headers to understand your remaining quota.
✅ Pause and retry after the
Retry-Aftertime if you receive a429.✅ Batch requests where possible (e.g., use campaign messaging instead of sending thousands of singles).
✅ Contact support if you expect high traffic and need a higher limit.
⚡ Note: Rate limits are applied per account, not per API key or IP address.
Last updated