Skip to main content

not_found

HTTP 404 · code: "not_found" · type: https://docs.formfeed.dev/errors/not-found

The object the request names does not exist in the workspace of the key, or the path does not exist at all. Templates, template versions and channels have codes of their own: template_not_found and channel_not_found.

Example​

{
"type": "https://docs.formfeed.dev/errors/not-found",
"title": "Not found",
"status": 404,
"detail": "Render not found",
"code": "not_found",
"request_id": "req_4b7c1e9a2f3d4c5b8a6e7f9012"
}

detail says what was not found: Render not found for a well-formed id that this workspace does not have, Unknown render id for a string that is no render id at all, No route for GET /renders for a path the API does not have.

Common causes​

  • An id from another workspace: every key sees only its own workspace, and a workspace's renders, jobs and files are not visible from another one, not even in the same organisation.
  • An id that is cut short or mistyped. Ids are a prefix and 32 hex digits (rnd_7da09ab6cd9946b798c187c2a9350852, job_…, fil_…); upper or lower case does not matter, and the UUID form is accepted as well.
  • A path without /v1 (/renders instead of /v1/renders), or a path that does not exist.
  • The file of a Word or PowerPoint template version that is no longer stored, or the /file of an HTML template version, which has none.
  • An event, webhook endpoint or formfeed listen session that does not exist in this workspace, or an endpoint that is disabled, for a resend.
  • A shared partial name the organisation does not have.
  • A formfeed login device code that is unknown or expired (The code expired; start the login again).

How to fix it​

  • Check that the key belongs to the workspace that created the object: GET /v1/account or formfeed whoami shows it.
  • Copy the id from the API's answer rather than typing it.
  • For templates, see template_not_found.

Retry?​

No. Retrying the same request gives the same answer; correct the id, the path or the key first.