Rate Limits

Information about API rate limiting and best practices for managing request volume.

Current Status

The Sent API currently operates under a fair usage policy without explicit rate limits. However, this may change in the future to ensure platform stability and fair access for all users.

Fair Usage Guidelines

While no hard limits are enforced, please follow these guidelines:

• Reasonable Request Volume: Keep request rates reasonable for your use case
• Bulk Operations: Implement throttling when sending bulk messages
• Retry Logic: Use exponential backoff for retries
• Monitor Responses: Watch for 429 status codes in case limits are implemented

Future Rate Limiting

When rate limits are implemented, you can expect:

Response Headers

• X-RateLimit-Limit: Maximum requests allowed
• X-RateLimit-Remaining: Requests remaining in current window
• X-RateLimit-Reset: Time when the limit resets

Error Response

{
  "status": 429,
  "title": "Too Many Requests",
  "detail": "Rate limit exceeded. Please retry after 60 seconds."
}

Best Practices

1. Implement Request Queuing

Queue messages during high-volume periods to smooth out request rates.

2. Use Webhooks

Instead of polling for status updates, use webhooks to receive real-time notifications.

3. Batch Processing

When processing large volumes, batch your requests and add delays between batches.

4. Monitor Your Usage

Track your API usage patterns to identify and optimize high-volume operations.

Rate Limit Exceptions

Contact support if you need higher rate limits for:

• Migration projects
• Seasonal campaigns
• Time-sensitive operations