Errors

`api_key_owner_inactive`

401. The key itself is fine, but the administrator who created it has left the account or been deactivated. The API checks this on every request, not only when the key is issued, so an integration that worked yesterday can start failing with this code. HTTP 401.

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

{
  "type": "https://docs.filmo.io/errors/api_key_owner_inactive",
  "title": "API key owner inactive",
  "status": 401,
  "code": "api_key_owner_inactive",
  "detail": "The user who created the API key is no longer active in the account",
  "requestId": "req_0b9f6c1d2e3a4f5a8b7c6d5e4f3a2b1c"
}

When it happens

401. The key itself is fine, but the administrator who created it has left the account or been deactivated. The API checks this on every request, not only when the key is issued, so an integration that worked yesterday can start failing with this code.

What to do

Issue a new key (or reconnect the integration) from an account that is still an administrator. Everything a key writes is attributed to its owner, so use a person who is meant to stay.

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