Rate Limits
The ColdSend API enforces rate limits to ensure platform stability and fair usage.Current Limits
| Limit | Value | Window |
|---|---|---|
| Requests | 100 | Per minute |
| Requests | 1,000 | Per hour |
Rate Limit Headers
Every API response includes rate limit information:| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum requests per window |
X-RateLimit-Remaining | Requests remaining in current window |
X-RateLimit-Reset | Unix timestamp when the window resets |
Handling Rate Limits
When You Hit the Limit
If you exceed the rate limit, the API returns: Status: 429 Too Many RequestsImplementing Backoff
Use exponential backoff to handle rate limiting gracefully:Checking Remaining Requests
Before making a request, check the headers from your last request:Best Practices
Batch Operations
When processing multiple items, space out your requests:Use Webhooks
For real-time updates instead of polling:- Configure webhooks for campaign events
- Receive notifications for opens, replies, and bounces
- Reduces the need for frequent API calls
Cache Responses
Cache frequently accessed data:Monitor Usage
Track your API usage:Rate Limit by Endpoint
All endpoints share the same rate limit pool. High-volume operations should be spread across time:| Operation | Typical Rate Impact |
|---|---|
| Create campaign | 1 request |
| Update campaign | 1 request |
| Delete campaign | 1 request |
| Add sender account | 1 request (includes validation) |
| Delete sender account | 1 request |
Contacting Support
If you need higher rate limits for your use case, contact [email protected] with:- Your account ID
- Expected request volume
- Use case description

