not_found · 1301 · HTTP 404

{
  "ok": false,
  "request_id": "req_…",
  "error": {
    "code": "not_found",
    "number": 1301,
    "message": "No such resource: an unknown job or monitor id (or one that belongs to someone else), or a channel or playlist that does not exist or is not public.",
    "docs": "https://transcriptfetch.com/docs/errors/not_found"
  }
}

Every failure carries error.code, error.number, error.message and error.docs, plus at most one of retry_with (the request change that would succeed), details (structured specifics) or issues (validation problems).

No such resource: an unknown job or monitor id (or one that belongs to someone else), or a channel or playlist that does not exist or is not public.

• The job id does not exist, or belongs to another account (both answer the same way, so ids cannot be enumerated).
• The monitor id does not exist, was deleted, or belongs to another account.
• The id was truncated or taken from a different environment.
• On /channel or /playlist, or when creating a monitor: the channel, profile or playlist does not exist, or is not publicly viewable (YouTube reports a deleted or unviewable playlist and an unknown handle this way). An existing channel with no uploads is a 200 with an empty list, not a 404.

• Use the job_id exactly as the 202 response or the batch entry returned it.
• List your monitors with GET /api/v2/monitors to find a monitor's id.
• For a listing, check the handle, id or URL against the platform; a private or deleted playlist cannot be listed by anyone.
• Poll with the same API key that created the job.