NOT_FOUND

HTTP status: 404

What it means

The requested resource does not exist.

Why it happens

• No resource with that id exists for your account. Ids never leak: another user's resource id answers the same way as a nonexistent one.

How to fix it

• Check the id (e.g. from the create response's Location header).
• Confirm you are using the API key of the account that owns the resource.

Example

Every non-2xx response uses the same envelope; path (when present) is the exact JSON path of the offending field, and requestId identifies the request in support conversations:

{
  "error": {
    "code": "NOT_FOUND",
    "message": "The requested resource was not found.",
    "docsUrl": "https://automotion.dev/docs/errors/not_found"
  },
  "requestId": "req_0123456789abcdef0123456789abcdef"
}

See the error index for the full catalog and the API overview for envelope semantics.