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

# Errors & status codes

HTTP status codes and the structure of API messages.

The API uses standard HTTP status codes to indicate the result of each request.

| Code  | Meaning      | When it happens                                           |
| ----- | ------------ | --------------------------------------------------------- |
| `200` | OK           | The request was processed successfully.                   |
| `401` | Unauthorized | The `authtoken` is missing or invalid.                    |
| `404` | Not found    | The route or resource does not exist (*Route not found*). |

## Message structure

Write and delete operations return an object with the status and a human-readable message:

```json
{
  "status": true,
  "message": "Client add successful."
}
```

On an authentication error:

```json
{
  "status": false,
  "message": "Invalid Auth Token."
}
```

{% hint style="info" %}
If you get *Route not found*, check the [routes with `index.php/`](/en/getting-started/conventions.md) section in Conventions.
{% endhint %}


---

# 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://developers.myscreators.com/en/getting-started/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.