Documents and signing

Use the Vendor API to upload document files, create reusable templates, and send signing requests. The reference groups these operations under documents, files, templates, and signing-requests.

Typical signing flow

1. Upload a source file with the files endpoints.
2. Create a document or template containing its signing requirements.
3. Create a signing request for the document and intended recipients.
4. Track request status and completion from your backend.
5. Retrieve the completed document when the request finishes.

Public signing routes

The API exposes public token routes for signing and verification. These routes cover opening a signing request, submitting completion, retrieving the public document, checking status, and verifying a public token.

Keep the management endpoints behind your authenticated backend. Only expose public token URLs that the signing flow explicitly gives to a recipient.

Workflows

For multi-step processes, use workflows to start, cancel, inspect status, complete steps, and inspect workflow analytics. The API reference is the source of truth for step types and payload fields.