Errors

not_found

404. The resource does not exist, or it exists outside the tenancy of the key; the API answers both the same way, so it never reveals that something exists. Archived orders also answer 404 on their GET, and a deleted record answers 404 from then on. HTTP 404.

HTTP status
404
Problem type
https://docs.filmo.io/errors/not_found

Example

{
  "type": "https://docs.filmo.io/errors/not_found",
  "title": "Not found",
  "status": 404,
  "code": "not_found",
  "detail": "Resource not found",
  "requestId": "req_0b9f6c1d2e3a4f5a8b7c6d5e4f3a2b1c"
}

When it happens

404. The resource does not exist, or it exists outside the tenancy of the key; the API answers both the same way, so it never reveals that something exists. Archived orders also answer 404 on their GET, and a deleted record answers 404 from then on.

What to do

Check the identifier and that the key belongs to the account (or to the parent account, for the resources that inherit from it) that owns the record. In a sync, a 404 on a record you already hold means it was deleted, archived or moved out of reach: confirm which before removing it on your side.

Retry

  • Fix and resendAny validation 4xx

    Fix the request and resend it; never in a loop.

Fields of errors[]

errors[].codestring

Stable code of the field error (required, must_not_be_null, invalid_type, invalid_value, too_small, too_big, unknown_field, invalid_format, not_found, must_be_after…). On a 409 conflict it says the cause: in_progress (another request with the same Idempotency-Key is still running), lock_timeout (another conditional write held the resource for more than five seconds) or invalid_state (the state of the resource forbids the operation).

Returned by

129 operations

Through MCP

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

Status