Documents API (removed)
Legacy multi-signer document API has been removed; use Waivers and signing routes instead.
The /v1/documents/* Partner API and the admin Documents hub (templates, sessions, field placement on PDFs) were removed in favor of a single waiver-based signing model.
What to use instead
- Partner API: See Waivers for signing and template-related operations that remain supported.
- Public signing: Token links use
/sign/[token]. Canonical JSON endpoints live under/api/sign/*(with/api/storefront/waiver/*kept as thin delegators for older clients). - Checkout / storefront: Waiver template fetch:
GET /api/sign/template(legacy:GET /api/storefront/waiver-template). Immediate sign during booking:POST /api/sign/waiver.
Historical behavior
For a full capability inventory of the removed stack (schema, session lifecycle, admin flows), see the internal spec: docs/specs/document-signing-v2-capabilities.md in this repository (not published on this docs site).