Skip to main content

​
Rate Limits & Quotas

WazzAPI enforces rate limits to ensure fair usage and system stability. Limits are applied based on your subscription plan.

​
Rate Limits

Basic Plan

60 req/min1,000 req/hour

Pro Plan

300 req/min10,000 req/hour

Enterprise

1,000 req/min50,000 req/hour

​
Headers

Every API response includes current rate limit status in the headers:
HeaderDescription
X-RateLimit-LimitYour maximum request limit for the current window.
X-RateLimit-RemainingRequests remaining in the current window.
X-RateLimit-ResetUnix timestamp when the limit resets.

​
Handling Rate Limits

When a limit is exceeded, the API returns 429 Too Many Requests. The response includes a Retry-After header indicating how many seconds to wait. 
HTTP/1.1 429 Too Many Requests
Retry-After: 60
X-RateLimit-Limit: 300
X-RateLimit-Remaining: 0

​
Best Practices

  1. Exponential Backoff: If you hit a limit, wait and retry with increasing delays.
  2. Monitor Headers: Programmatically check X-RateLimit-Remaining to throttle your own requests before hitting the limit.
  3. Queueing: Use a message queue (like RabbitMQ or Redis) to smooth out bursty traffic.

​
Message Quotas

In addition to request rate limits, plans have monthly message quotas:
  • Basic: 1,000 messages
  • Pro: 10,000 messages
  • Enterprise: Custom
Exceeding the message quota results in a 429 Quota Exceeded error.