# Error Responses

### 💬 **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.<br>

#### **Error Codes**

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