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

# Error Codes

The most common API error code responses are described below.

Please note that error codes described bellow are general errors, for specific method errors see error responses for each method.

| HTTP Status                 | Reason              | Description                      |
| --------------------------- | ------------------- | -------------------------------- |
| 401 (Unauthorized)          | BadCredentials      | API credentials are not correct  |
| 404 (Not Found)             | PageNotFound        | Page, action or record not found |
| 404 (Not Found)             | RecordNotFound      | Record not found                 |
| 422 (Unprocessable Entity)  | UnsupportedInput    | API credentials are not valid    |
| 500 (Internal Server Error) | InternalServerError | Server error                     |

Response example:

JSON

```
{
    "status": "error",
    "status_code ": 404,
    "message": {
        "customer_id": "Invalid customer_id"
    }
}
```


---

# 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://developer.citypay.io/introduction/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.