*REST API › Errors*

# `unauthorized`

> 401. The request was not authenticated: no API key arrived as a bearer token in the `Authorization` header. Every operation requires one. Without an `Accept-Language` header the body of this error is in Spanish, because there is no key owner to ask. HTTP 401.

HTTP status: `401` · Problem type: `https://docs.filmo.io/errors/unauthorized`

## When it happens

401. The request was not authenticated: no API key arrived as a bearer token in the `Authorization` header. Every operation requires one. Without an `Accept-Language` header the body of this error is in Spanish, because there is no key owner to ask.

## What to do

Send `Authorization: Bearer <key>` on every request, with a key created in the API and MCP settings of the app (Ajustes → API y MCP). Send `Accept-Language: en` to get the messages in English.

## Retry

| Condition | What to do | Note |
| --- | --- | --- |
| 401 · 402 · 403 (key, owner or plan) | Stop | Do not retry: resending the same request fails again. Act on the key, its owner or the plan: use a valid key with the right scope, ask an administrator for the missing permission, or add the add-on. |

## Example

*unauthorized*

```json
{
  "type": "https://docs.filmo.io/errors/unauthorized",
  "title": "Unauthorized",
  "status": 401,
  "code": "unauthorized",
  "detail": "Missing Authorization header: Bearer <api key>",
  "requestId": "req_0b9f6c1d2e3a4f5a8b7c6d5e4f3a2b1c"
}
```

## Returned by

`unauthorized` can be returned by any operation.

## Through MCP

A tool call that fails comes back with `isError` set and the problem as structured content, with the same `code`.

---

Canonical URL: https://docs.filmo.io/rest-api/errors/unauthorized  
Last updated: 2026-10-25