SignEnvoy docs
Sign in Start in the sandbox

Error reference Signing link invalid or expired

Error reference

Signing link invalid or expired

The signing link is unknown, superseded, or no longer usable.

Problem type /problems/token-invalid
HTTP status 404
Emitted by Signing page, REST API (/v1)
Title values
Signing link invalid or expired
This signing link is invalid or has expired
Trigger
REST API (/v1): signing token unknown or dead
Signing page: unknown/dead signing link (also the deliberate fallback when a dead link is not classifiable — no probe oracle)

What happened

A signing link token did not resolve to an active recipient. The response is HTTP 404.

What it means

Tokens rotate when a document is re-sent or a reminder goes out, so an older link stops working on purpose. A link that was declined is also reported this way: the API does not confirm whether a dead link ever existed. When the link can be classified (expired, withdrawn, declined, document expired), the signing page receives the more specific slug instead.

What to do next

For a recipient: use the most recent email from the sender, or ask them to re-send. For an integration: this slug on the REST API means the token you passed to a ceremony endpoint is not current; mint a fresh link for that recipient with POST /v1/documents/{id}/recipients/{recipient_id}/signing-link (see signing links), or .../embed-session for an embedded ceremony.

Problem body

Every error the API returns 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/token-invalid",
  "title": "This signing link is invalid or has expired",
  "status": 404,
  "instance": "/v1/...",
  "docs_url": "https://staging.signenvoy-docs-b4g.pages.dev/errors/token-invalid"
}