Send documents

Create draft documents from your product using the Upsign API. Upload files and add recipients, then redirect users to the draft in Upsign to complete sending the document out for signature.

Create drafts

Create draft documents from your application through the Upsign API. Store the returned id in your system to reference, monitor, and manage document workflows over time.

Create draft API reference

Upload files

Attach source files when you create or update a draft so Upsign can prepare the document for signing.

• Include a file part in the multipart request (supported types depend on server validation — commonly PDF, images, and common office formats).
• Large uploads should be sent from your server to keep keys and payloads off the client.

See the Create draft API reference for multipart fields including file.

Add recipients

Define who needs to sign or receive the document and in what order.

• Pass recipients as a JSON array string in the multipart body (for example signers with email, name, and role).
• Configure signing order and roles to match your workflow before you send the signature request.

See the Create draft API reference for multipart fields including recipients.

Send documents to sign

Sending documents out for signature currently happens within Upsign. After you create a draft, store its public identifier id (a doc_* value) and use it to redirect the user to that document in the Upsign app to continue the sending flow.

• Document URL: https://app.upsign.com/documents?d={doc_*} (URL-encode the id value)

Next steps

• Launch workflows
• Webhooks overview
• Authentication