API Error Codes

When an API request fails, Murf returns an error code instead of the expected response. These error codes help identify why the request could not be processed.

Example:

A request to convert "Hello World" using the Speech API may return:

Error Code: 400
Message: Invalid Voice ID

Table of Contents

• User Errors (4xx Status Codes)
• 400 – Bad Request
• 402 – Payment Required
• 429 – Too Many Requests
• Platform Errors (408 & 500 Status Codes)
• 408 – Request Timeout
• 500 – Internal Server Error

User Errors (4xx Status Codes)

User errors indicate that there is an issue with the API request.

A 400 Bad Request error may occur for the following reasons:

• Invalid Voice ID
• Multinative locale not supported
• Invalid Speed value
• Character limit exceeded (more than 3000 characters)

402 – Payment Required

A 402 Payment Required error indicates that all available characters have been consumed and additional credits are required.

429 – Too Many Requests

A 429 Too Many Requests error occurs when the concurrency limit has been exceeded.

If you encounter this error, check which region you are using. Try the Global region for up to 15 concurrent requests. If you require higher concurrency or a specific region, use the EY region.

Platform Errors (408 & 500 Status Codes)

Platform errors indicate an issue with the API infrastructure.

A 408 Request Timeout error means the request took longer than the timeout limit.

Possible reasons include:

• Servers are overloaded
• Processing is taking too long
• Network connectivity issues
• A temporary infrastructure issue

500 – Internal Server Error

A 500 Internal Server Error indicates an unexpected issue with the API infrastructure that prevented the request from being processed.

Need Additional Help?

Contact Murf Support and include:

• The HTTP status code
• The complete error message
• The API endpoint used
• The request timestamp
• Your Request ID (if available)

Providing these details will help us investigate the issue more quickly.