Transactions Per Second (TPS)
Each API key is assigned a maximum throughput measured in Transactions Per Second (TPS). For example:| API Key | TPS |
|---|---|
| OTP API Key | 10 TPS |
| Notifications API Key | 25 TPS |
Viewing Your Limits
You can view the throughput limit assigned to each API key from the Zeckta Dashboard. Navigate to:Rate Limit Headers
Every request includes standard rate limit headers.| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum requests allowed per second. |
X-RateLimit-Remaining | Remaining requests available in the current window. |
X-RateLimit-Reset | Unix timestamp when the current window resets. |
Retry-After | Seconds to wait before retrying (returned with 429 responses). |
Exceeding Limits
When your application exceeds the configured TPS limit, requests are rejected. Response:Abuse Protection
Repeated rate limit violations may trigger temporary protection measures. In these cases, requests may continue to receive:Recommended Practices
Implement Retries
Use exponential backoff when retrying failed requests.Use Campaigns for Bulk Messaging
For large recipient volumes, prefer SMS Campaigns over individual message requests.Monitor Throughput
Ensure your application does not consistently operate at its maximum TPS allocation.Respect Retry Headers
Always honor theRetry-After header before retrying requests.