Error Responses

A reference guide outlining how the system communicates issues during API interactions, helping developers understand, handle, and resolve errors gracefully.

💬 Error Responses

This section describes the possible error responses you may encounter when interacting with the Bodhi API, applicable to both streaming and non-streaming modes. Errors typically arise from issues such as invalid configurations, authentication failures, account-related problems, or server-side issues. In the event of an error after a WebSocket connection is established, the server will send an error message before closing the connection.

Error Codes

Status Code	Error Type	Description	Intervention
400	Bad Request	Invalid configuration sent via WebSocket, such as malformed JSON, invalid transaction_id, or unavailable model.	Consult the documentation to ensure appropriately configured connection request. Note the error message for help.
401	Unauthorized	Missing or incorrect x-customer-id or x-api-key header.	Check bodhi.navana.ai for your customer_id, api_key pairing.
402	Insufficient Balance	The account does not have enough credits to process the ASR request.	Contact [e-mail] to purchase more credits.
403	Inactive Customer	The customer account is deactivated and cannot process requests.	Contact [e-mail] to enquire about account activation.
500	Internal Server Error	Unexpected server error or panic during request handling.	Retry the request after a brief delay. If the issue persists, capture logs and contact [e-mail] with the transaction ID and timestamp.
503	Service Unavailable	The server is currently unavailable or temporarily overloaded.	The server may be overloaded or undergoing maintenance. Retry the request after a brief delay.