> For the complete documentation index, see [llms.txt](https://enoch-app.gitbook.io/enoch/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enoch-app.gitbook.io/enoch/api-references/enoch-rest-apis/response-codes-and-types.md).

# Response codes & types

The Avatar API uses conventional HTTP response codes to indicate the success or failure of an API request.

* Codes in the **`2xx`** range indicate success. 
* Codes in the **`4xx`** range indicate a failure given the information provided. 
* Codes in the **`5xx`** range indicate an error with Enoch Player Me services.

Timestamps return in UTC time.

| Status Code          | Description                                                              |
| -------------------- | ------------------------------------------------------------------------ |
| 200 - OK             | Everything worked as expected.                                           |
| 400 - Bad Request    | The request was unacceptable, often due to missing a required parameter. |
| 401 - Unauthorized   | Unauthorized request for a secured endpoint.                             |
| 402 - Request Failed | The parameters were valid but the request failed.                        |
| 403 - Forbidden      | The authorized user doesn't have permission to perform the request.      |
| 404 - Not Found      | The requested resource doesn't exist.                                    |
| 5xx - Server Errors  | Something went wrong on Enoch's end.                                     |

## Avatar file format

All 3D avatars are delivered in GLTF format. 

The API returns standardized .gltf or .png files for the 3D and 2D avatars, or JSON-encoded responses. Only default HTTP response codes are used.

glTF is a standard file format for three-dimensional scenes and models. A glTF file uses one of two possible file extensions: .gltf or .glb. Both .gltf and .glb files may reference external binary and texture resources


---

# 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://enoch-app.gitbook.io/enoch/api-references/enoch-rest-apis/response-codes-and-types.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.