Skip to main content
The Audixa API uses standard HTTP status codes to indicate the success or failure of requests. This guide documents all possible error responses.

Error Response Format

All error responses follow a consistent JSON format:
Some errors may include additional context:

HTTP Status Codes

Success Codes

Client Error Codes

Server Error Codes

WebSocket Close Codes

Common Errors

400 Bad Request

Returned when request parameters are missing or invalid.
Common causes:
  • Missing required fields (text, voice_id, model)
  • Invalid model value (must be base or advanced)
  • Text exceeds maximum length

401 Unauthorized

Returned when authentication fails.
Common causes:
  • Missing x-api-key header
  • Invalid or revoked API key

402 Payment Required

Returned when your account has insufficient balance.
Solution: Add funds via the Billing Dashboard.

404 Not Found

Returned when a requested resource doesn’t exist.
Common causes:
  • Invalid generation_id when checking status
  • Generation expired (older than 24 hours)

429 Too Many Requests

Returned when you exceed the rate limit.
Solution: Implement exponential backoff retry logic. See Rate Limits.

500 Internal Server Error

Returned when an unexpected server error occurs.
Solution: Retry the request. If the error persists, contact support@audixa.ai.

Error Handling Example

Both SDKs provide typed error classes for robust error handling: