API rate limits and best practices

API Rate Limits

To ensure fair usage and service stability, API requests are rate-limited:

Best Practices

• Use webhooks — Instead of polling, configure webhooks to get notified when an SMS arrives.
• Cache responses — Cache service and country lists as they do not change frequently.
• Handle errors gracefully — Always check the HTTP status code and implement retry logic with exponential backoff for 429 (Too Many Requests) responses.
• Use idempotency — For critical operations, include an idempotency key to prevent duplicate orders.

Error Codes

• 401 — Invalid or missing API key
• 422 — Validation error (check the response body for details)
• 429 — Rate limit exceeded
• 500 — Server error (retry after a short delay)