Error · 404

job_not_found

Job not found

What happened

No async job matches that id.

What to do

Poll with the jobId from the handle the starting operation returned — {jobId, kind, status, pollWith} — never an id you constructed.

The response body carries a recovery object with the same guidance in machine-readable form: recovery.action names the call to make next, and recovery.hint is one sentence a model can act on. Not every code carries one — a 401, for instance, has nothing to recover to but a valid token.

not_found — Not found
service_not_found — Service not found
invoice_not_found — Invoice not found
record_not_found — DNS record not found
mailbox_not_found — Mailbox not found
database_not_found — Database not found
pending_action_not_found — Pending action not found

Back to the full error reference

404 application/problem+json

{9 keys}

:"https://api.inleed.com/errors/job_not_found",

:"Job not found",

:404,

:"No async job matches that id.",

:"job_not_found",

:"/api/v1/…",

:"req_01hxa3b4c5d6e7f8g9h0j1k2m3",

:"2026-08-29T12:34:56.000Z",

:{2 keys}

:"…",

:"Poll with the jobId from the handle the starting operation returned — {jobId, kind, status, pollWith} — never an id you constructed."

}

Click a key to copy its jq path.

Handling it

// Branch on code, never on title or detail — those are written for
// humans and may change wording at any time.

if (problem.code === 'job_not_found') {
  // Poll with the jobId from the handle the starting operation returned — {jobId, kind, status, pollWith} — never an id you constructed.
}

What happened

What to do

Other 404 responses