> ## Documentation Index
> Fetch the complete documentation index at: https://developers.phrase.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Errors

Every error response is an [RFC 9457](https://www.rfc-editor.org/rfc/rfc9457) problem details object, sent as `application/problem+json`. Base your error handling on `code`, which doesn't change. `title` and `detail` are written for people and may be reworded. When Orchestrator knows more about a particular error, such as why a token was rejected or when to retry, `detail` says so.

```json theme={null}
{
  "type": "https://developers.phrase.com/en/api/orchestrator/errors#not_found",
  "title": "Not Found",
  "status": 404,
  "detail": "The resource doesn't exist, or the authenticated user can't access it.",
  "code": "not_found"
}
```

A `422` can have several causes, so it also lists each one in `errors`, with a `detail` and, when the cause is tied to a field, a `pointer` to that field as a [JSON Pointer](https://www.rfc-editor.org/rfc/rfc6901):

```json theme={null}
{
  "type": "https://developers.phrase.com/en/api/orchestrator/errors#unprocessable_content",
  "title": "Unprocessable Content",
  "status": 422,
  "detail": "A parameter doesn't match its schema, or the change isn't allowed in the resource's current state. Each entry in `errors` describes one cause.",
  "code": "unprocessable_content",
  "errors": [
    {
      "detail": "can't be blank",
      "pointer": "/name"
    },
    {
      "detail": "Only locked revisions can be renamed."
    }
  ]
}
```

A `401` also carries a `WWW-Authenticate: Bearer` header, as defined in [RFC 6750](https://www.rfc-editor.org/rfc/rfc6750#section-3), with `error="invalid_token"` when a token was sent but rejected.

| Code | Status | Meaning |
| - | - | - |
| `bad_request` | 400 | The request is malformed, for example its body isn't valid JSON. |
| `unauthorized` | 401 | The request has no valid Phrase Platform JWT issued for Orchestrator. Send one as `Authorization: Bearer <JWT>`. |
| `forbidden` | 403 | The authenticated user isn't allowed to perform this action on the resource. |
| `not_found` | 404 | The resource doesn't exist, or the authenticated user can't access it. |
| `request_timeout` | 408 | The request body arrived too slowly. Retry the request. |
| `content_too_large` | 413 | The request body is larger than 8 MB. |
| `unprocessable_content` | 422 | A parameter doesn't match its schema, or the change isn't allowed in the resource's current state. Each entry in `errors` describes one cause. |
| `rate_limited` | 429 | The authenticated user's rate limit is used up. Retry after the number of seconds in the `Retry-After` header. |
| `internal_server_error` | 500 | Orchestrator failed unexpectedly. A write may or may not have been applied, so check the resource before retrying it. |

A `502`, `503` or `504` comes from the load balancer in front of Orchestrator, not from Orchestrator itself, and has no JSON body.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.