Errors

`api_key_invalid`

401. The key in the request is not one the API recognises: its prefix, its length or its hash does not match any key. With no key owner to ask, the body is in Spanish unless you send Accept-Language. HTTP 401.

HTTP status: 401
Problem type: https://docs.filmo.io/errors/api_key_invalid

{
  "type": "https://docs.filmo.io/errors/api_key_invalid",
  "title": "Invalid API key",
  "status": 401,
  "code": "api_key_invalid",
  "detail": "The API key is not valid",
  "requestId": "req_0b9f6c1d2e3a4f5a8b7c6d5e4f3a2b1c"
}

When it happens

401. The key in the request is not one the API recognises: its prefix, its length or its hash does not match any key. With no key owner to ask, the body is in Spanish unless you send Accept-Language.

What to do

Copy the key again from where you stored it; a key is shown only once, when it is created. If you no longer have it, an administrator creates a new key in the API and MCP settings of the app (Ajustes → API y MCP).

Retry

Stop401 · 402 · 403 (key, owner or plan)
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.

Returned by

api_key_invalid 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`.

Was this page helpful?

Example

When it happens

What to do

Retry

Returned by

Through MCP