> For the complete documentation index, see [llms.txt](https://docs.eseye.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eseye.com/api-reference/api-conventions/error-handling.md).

# Error handling

Interpret HTTP responses and resolve API errors.

Eseye APIs use HTTP status codes to report request outcomes.

### HTTP status codes

| Status             | Meaning                                    | What to do                             |
| ------------------ | ------------------------------------------ | -------------------------------------- |
| `200 OK`           | The request succeeded.                     | Process the response.                  |
| `400 Bad Request`  | The request is malformed.                  | Check parameters and request data.     |
| `401 Unauthorized` | The token is missing, invalid, or expired. | Check the header or request a token.   |
| `403 Forbidden`    | The service account lacks permission.      | Request the required access.           |
| `404 Not Found`    | A resource does not exist.                 | Check the supplied identifiers.        |
| `5xx`              | Eseye could not complete a valid request.  | Retry temporary failures with backoff. |

### Error responses

An error can include `errorCode`, `errorTag`, `message`, and `additionalDetails`.

### Handle errors safely

* Record the HTTP status and error details in application logs.
* Do not log client secrets or complete access tokens.
* Correct most `4xx` errors before retrying.
* Retry temporary network and `5xx` failures with exponential backoff.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.eseye.com/api-reference/api-conventions/error-handling.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.