> For the complete documentation index, see [llms.txt](https://doc.xendbridge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.xendbridge.com/errors.md).

# Errors

XendBridge is a REST API product and as such we religiously follow conventional HTTP response codes to indicate the status of an API call - success or failure.

> 👍2XX Status code\
> Everything went well.

> 🚧4XX Status code\
> A required piece of information/data was not found in the API request thus we cannot process it

> ❗5XX Status code\
> Something is wrong with XendBridge. This range of errors are extremely rare

<table><thead><tr><th width="150">Status Code</th><th>Meaning</th></tr></thead><tbody><tr><td>200, 201, 204</td><td>Everything works as expected. API request was successful</td></tr><tr><td>400</td><td>Bad request. Review the data sent in the request. Usually, this means a required piece of information is missing</td></tr><tr><td>401</td><td>Unauthorized. This happens when you provide an invalid or non-existent API key</td></tr><tr><td>404</td><td>Resource not found. This could happen when you try to retrieve an item with a non-existent ID</td></tr><tr><td>403</td><td>Not enough permission to perform this operation</td></tr><tr><td>5XX</td><td>Something went wrong on XendBridge end. Doesn't happen often :)</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://doc.xendbridge.com/errors.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.