Rate limits and quotas - YALG Developer Docs

YALG enforces both monthly quotas and per-minute rate limits for API-key traffic.

Default limits

Enterprise plans can override monthly API calls and per-minute limits.

Header	Description
`X-RateLimit-Limit`	Per-minute request limit.
`X-RateLimit-Remaining`	Requests remaining in the current minute window.
`X-RateLimit-Reset`	Time when the current minute window resets.
`X-Quota-Limit`	Monthly API call quota.
`X-Quota-Remaining`	Monthly calls remaining.
`X-Quota-Reset`	Time when the monthly quota resets.
`Retry-After`	Seconds to wait before retrying a `429` response.

When quota or rate limits are exceeded, YALG returns 429 Too Many Requests. Use the Retry-After header when present before retrying.

{
  "statusCode": 429,
  "message": "Rate limit exceeded",
  "error": "Too Many Requests"
}

Retry 429 responses after Retry-After.
Use exponential backoff for transient 5xx responses.
Do not retry validation errors until the payload is fixed.
Avoid high-frequency polling when job status can be checked at a slower cadence.