SignEnvoy docs

Error reference / not-found

Not found

The resource does not exist, or it belongs to another workspace.

Problem type /problems/not-found
HTTP status 404
Emitted by Signing page, REST API (/v1)
Title values
Not found
Unknown field
Trigger
REST API (/v1): resource absent or cross-tenant (indistinguishable by construction, §3.6)
Signing page: unknown field id

What happened

The request named an object (a document, template, key, webhook endpoint, or field) that the API could not find. The response is HTTP 404.

What it means

A missing object and an object owned by a different workspace are deliberately indistinguishable: the API never confirms that an id exists outside your workspace. On the signing page the same slug means the field id in the request is unknown for that signing link.

What to do next

Check the id you sent against the one the API returned when the object was created, and confirm the API key belongs to the workspace that owns it. Ids are prefixed (doc_, tpl_) and case-sensitive.

Problem body

Every error is an RFC 9457 problem document with media type application/problem+json. The type member is the stable identifier to switch on; docs_url is this page. 

{
  "type": "/problems/not-found",
  "title": "Not found",
  "status": 404,
  "instance": "/v1/...",
  "docs_url": "https://docs.signenvoy.com/errors/not-found"
}