*REST API › Errors*

# `forbidden`

> HTTP HTTP 403.

HTTP status: `403` · Problem type: `https://docs.filmo.io/errors/forbidden`

## When it happens

403. The key is correct, but its owner lacks the module, organization or administrator permission the operation demands. This is about the owner of the key; [`insufficient_scope`](https://docs.filmo.io/rest-api/errors/insufficient_scope) is about the key and [`addon_required`](https://docs.filmo.io/rest-api/errors/addon_required) is about the plan.

## What to do

An administrator of the account grants the owner the missing permission, or you use a key owned by someone who has it. Changing the key's scopes does not help.

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

*forbidden*

```json
{
  "type": "https://docs.filmo.io/errors/forbidden",
  "title": "Forbidden",
  "status": 403,
  "code": "forbidden",
  "detail": "You are not allowed to perform this operation",
  "requestId": "req_0b9f6c1d2e3a4f5a8b7c6d5e4f3a2b1c"
}
```

## Returned by

`forbidden` 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/forbidden  
Last updated: 2026-10-25