Introduction to the Undersign API

The Undersign API provides programmatic access to electronic-signature workflows. Create signature requests, work with reusable templates, manage signers and retrieve signing status from your own applications.

What the API supports

The currently documented API supports:

• Creating signature requests
• Reusable templates
• Multiple signers per request
• Sequential signing configuration
• Field visibility configuration
• External IDs
• Metadata
• Webhook configuration
• Retrieving signature request status
• Listing templates
• Retrieving template details
• Retrieving categories

A typical workflow

The most common flow moves from authentication through to status retrieval:

1. Authenticate

   Pass your bearer token with every request. See Authentication.

2. List templates

   Retrieve the templates available to your account with GET /templates.

3. Choose a template

   Pick the template_id you want to send. Inspect its signers and fields with Get Template Details when needed.

4. Provide signers

   Supply the name and email for each signer assigned to the template.

5. Create the signature request

   Call POST /signature-requests with the template and signer details.

6. Store returned identifiers

   Keep the returned package_id and package_guid with your internal record.

7. Check status

   Retrieve request status with GET /signature-requests/{package_guid}, or receive webhook notifications.

Next steps