Skip to main content

​
Overview

The Yala API applies rate limits so that usage stays fair and stable for all customers. If you exceed the limits, you will receive HTTP 429 Too Many Requests and should back off before retrying.

​
Limits

Limit typeValueDescription
Rate5 requests per secondSustained request rate per second.
Quota10,000 requests per monthTotal number of requests allowed per calendar month for your API key.
Limits are applied per API key (and may be per tenant in production). Different environments (e.g. sandbox vs production) may have separate limits.

​
When you are rate limited

  • The API responds with HTTP 429 and a body that may include a Retry-After hint or a message about rate limiting.
  • Recommended behavior: Use exponential backoff (e.g. 1s, 2s, 4s) and optional jitter before retrying. Do not retry immediately in a tight loop.

​
Best practices

  • Throttle client-side: Keep your request rate at or below 5 requests per second in normal operation.
  • Monitor quota: Track your monthly request count so you stay under 10,000 requests per month, or contact developers@useyala.com to discuss higher limits.
  • Cache when possible: Use cached data (e.g. pairs, methods) where the API allows to reduce unnecessary calls.
For high-volume or batch use cases, contact developers@useyala.com to discuss custom rate limits or quotas.