# HTTP error status codes

If an API call is invalid, a JSON response body will return with the following response format. Please review the table within each section to view specific return responses.

| Status code                        | Description                                                               |
| ---------------------------------- | ------------------------------------------------------------------------- |
| `400 Bad Request`                  | The request was unaccceptable, often due to missing a required parameter. |
| `401 Unauthorized`                 | Authentication was invalid.                                               |
| `402 Request Failed`               | The parameters were valid but the request failed.                         |
| `404 Not Found`                    | The requested resource doesn't exist.                                     |
| `409 Conflict`                     | The request conflicts with another request.                               |
| `429 Too Many Requests`            | Too many requests hit the API too quickly.                                |
| `500, 502, 503, 504 Server Errors` | Something went wrong (server error).                                      |

**Note:** If a table is not present in the section, the API response is not returned in a standard format.

```


    "status": "{See Table}",
    "timestamp": 1523517241,
    "error": "{See Table}",
    "message": "{See Table}"
}
```


---

# 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://teamhycon.gitbook.io/docs/api-v1/api-response/http-error-status-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.