> For the complete documentation index, see [llms.txt](https://6dot50.gitbook.io/6dot50-apis/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://6dot50.gitbook.io/6dot50-apis/pay-api/response-models.md).

# Response Models

Each operation may return one of the following HTTP responses, depending on the operation and action performed.

### 200 Successful

Successful response models vary per operation and are detailed in the sections that follow.

### 400 Bad Request

A bad request response will be returned for any operations that fail validation, e.g. uniqueness, malformed type, etc.

An error message is returned in the body of the response.

### 404 Not Found

A not found response will be returned when referencing an entity that does not exist, e.g. fetching a Batch with an `id` that does not exist.

### 401 Unauthorised

A 401 HTTP status code will be returned should an invalid Bearer token be supplied as part of a request’s Header, or if the Bearer token supplied has expired.

### 500 Server Error

A server errors when an unhandled exception is thrown by the Redemptions API. The exception will be returned within the response body.

Please contact 6DOT50 [Support](/6dot50-apis/support-1.md) with the error.


---

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

```
GET https://6dot50.gitbook.io/6dot50-apis/pay-api/response-models.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.