Skip to main content
Audixa applies rate limits to ensure fair usage and maintain service quality for all users. This guide explains the limits and how to handle them.

Rate Limit Tiers

Rate limits apply per API key. Contact sales@audixa.ai for custom enterprise limits.

Rate Limit Headers

Every API response includes headers showing your current rate limit status: Example response headers:

Handling Rate Limits

When you exceed the rate limit, the API returns a 429 Too Many Requests error:
Both the Python and Node.js SDKs have built-in retry logic that automatically handles rate limits with exponential backoff. You only need to implement manual retry logic if you’re using the REST API directly.

SDK Error Handling

Manual Retry Strategy (REST API)

If using the REST API directly, implement exponential backoff:

Best Practices

Batch Requests

Combine multiple short texts into fewer requests when possible.

Implement Backoff

Use exponential backoff when retrying failed requests.

Monitor Usage

Check rate limit headers to track your usage.

Cache Results

Store generated audio to avoid regenerating the same content.

Need Higher Limits?

If you’re hitting rate limits regularly, consider:
  1. Upgrading your plan for higher per-minute limits
  2. Contacting sales for custom enterprise limits
  3. Optimizing your code to reduce unnecessary requests

Contact Sales

Discuss custom rate limits for your enterprise needs.