> For the complete documentation index, see [llms.txt](https://docs.ocaindonesia.co.id/call-api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ocaindonesia.co.id/call-api/response-code/error-codes.md).

# Error Codes

This error codes is additional information to explain what happened when some errors occured. The following table describe the code which may appear when working with OCA CALL Gateway. If an error is not listed in the table, going back to HTTP status codes above in order to determine the best way to address the issues.

<table><thead><tr><th width="86">Code </th><th width="164">Text</th><th>Description</th></tr></thead><tbody><tr><td><mark style="color:red;">5</mark></td><td>low-balance</td><td>Indicationg that your account has no enough balance left</td></tr><tr><td><mark style="color:red;">9</mark></td><td>Too Many Request Code</td><td>Due to the api rate limit, you have to wait until the currently window wxpires, the default api rate limit is in 25 request per seconds. You can check http headers reaponse in order to know the remaining limit of your request.<br><strong>- </strong><mark style="color:red;"><strong>X-RateLimit-limit</strong></mark><strong> :</strong> the rate limit of endpoint<br>- <mark style="color:red;"><strong>X-RateLmit-Remaining</strong></mark> : the number of request left<br>- <mark style="color:red;"><strong>X-RateLimit-Reset</strong></mark> : the remaining window before the rate limit resets</td></tr><tr><td><mark style="color:red;">13</mark></td><td>Internal Error</td><td>Corresponds with HTTP 500.<br>An unknown internal error occured</td></tr><tr><td><mark style="color:red;">19</mark></td><td>Missing Authorization Header</td><td>Corresponds with HTTP 401.<br>It indicates Authorization header is not set properly</td></tr><tr><td><mark style="color:red;">33</mark></td><td>Data doesn't exist</td><td>Corresponds with HTTP 404.<br>The certain data is not found</td></tr><tr><td><mark style="color:red;">39</mark></td><td><em>[object]</em></td><td>Corresponds with HTTP 406.<br>There are incorrects or missing parameter in request body, it is like the message_value is not same as the template message</td></tr><tr><td><mark style="color:red;">43</mark></td><td>Auth token is not supplied</td><td>Corresponds with HTTP 401.<br>It indicates Authorization header is not set properly</td></tr><tr><td><mark style="color:red;">45</mark></td><td>Auth token is not valid</td><td>Corresponds with HTTP 401.<br>It indicates Authorization token is not valid</td></tr><tr><td><mark style="color:red;">59</mark></td><td>Whatsapp Template doesn't exist Code</td><td>Corresponds with HTTP 406.<br>Your message template doesn't exist</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ocaindonesia.co.id/call-api/response-code/error-codes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.