# Error codes

If an error occurs on Hub88 side, Hub88 will respond with an HTTP error code and a JSON object with a text message. 

{% code title="Error format: " %}

```json
{"error": <error description>}
```

{% endcode %}

Below is the list of error codes that can be returned by the Hub88 APIs:&#x20;

| HTTP Error Code | Description                                                                      |
| --------------- | -------------------------------------------------------------------------------- |
| 400             | Invalid or missing request parameters.                                           |
| 401             | Request signature is invalid. Signature header **x-hub88-signature** is missing. |
| 403             | The **currency, country or game** isn't enabled for the Operator.                |
| 404             | The **country, currency or game** requested doesn't exist.                       |
| 404             | The **operator\_id** doesn't correspond to any existing Operator.                |
| 404             | The resource requested wasn't found.                                             |
| 500             | Internal server error.                                                           |


---

# Agent Instructions: 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:

```
GET https://docs.hub88.io/developer-docs/operator-api-reference/operator-api-overview/error-codes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.