Skip to main content
Zeckta applies rate limits to protect platform stability and ensure fair usage across all customers. Rate limits are enforced on a per API key basis.

​
Transactions Per Second (TPS)

Each API key is assigned a maximum throughput measured in Transactions Per Second (TPS). For example: The configured TPS determines how many requests can be processed each second.

​
Viewing Your Limits

You can view the throughput limit assigned to each API key from the Zeckta Dashboard. Navigate to:
The TPS column displays the current throughput configured for each key.

​
Rate Limit Headers

Every request includes standard rate limit headers. Example:

​
Exceeding Limits

When your application exceeds the configured TPS limit, requests are rejected. Response:
Example:
The response includes:
indicating how long to wait before retrying.

​
Abuse Protection

Repeated rate limit violations may trigger temporary protection measures. In these cases, requests may continue to receive:
with a longer retry period. Example:

​
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 the Retry-After header before retrying requests.

​
Need Higher Limits?

If your application requires additional throughput, contact Zeckta support to discuss higher TPS allocations.