Skip to main content
After the user signs, your backend creates the final PDF using the SuperDoc API.

Flow

Complete example

Download/PDF generation

Handle download requests to generate PDFs on-demand:

Data structure

The frontend sends the onSubmit payload plus a document reference and signer details your backend can access:

Signer fields

When forwarding this payload to POST /v1/sign, only the following signer fields are accepted: No other properties are accepted on signer: the request is rejected with a validation error if extra keys are sent. For application-specific context (tenantId, contractId, etc.), pass a top-level metadata object instead.
Do not trust ip or userAgent values from the browser-submitted payload. Derive them server-side from the incoming request (e.g. req.ip, req.headers['user-agent']) before forwarding to /v1/sign, so the audit trail certificate reflects what your server actually observed.

API reference