How Do I Build Custom Signing Workflows with an eSignature API?

A signing workflow defines who signs a document, in what order, what role each person plays, and what happens when each step is completed. eSignature API gives you full control over all of these.

Sequential signing (one after another)

In a sequential workflow, recipients sign in a defined order. The document is sent to signer 1 first. Once signer 1 completes, it automatically moves to signer 2, and so on. No recipient sees the document until the previous step is done.

Common use cases: employee signs an offer letter first, then HR countersigns. A customer signs a contract, then an account manager countersigns.

Set up sequential signing by assigning an order parameter to each signer in your API call.

Parallel signing (all at once)

In a parallel workflow, all recipients receive the document at the same time and can sign independently in any order. The document is considered complete when all parties have signed.

Common use cases: multi-party NDAs where all parties sign simultaneously. Partnership agreements with no preferred signing order.

Set up parallel signing by omitting the order parameter or setting all signers to the same order value.

Recipient roles

eSignature API supports five distinct recipient roles:

• Signer: Signs the document. The primary role.
• Approver: Reviews and approves without adding a signature field.
• Viewer: Receives a copy to view but does not sign or approve.
• Form filler: Fills in data fields (text, checkboxes, dropdowns) without signing.
• Carbon copy (CC): Receives a copy of the completed document on signing completion.

Combining roles lets you build complex workflows. For example: a form filler completes employee data first, then the employee signs, then HR countersigns, then a CC copy goes to payroll.

Setting envelope expiration

Add an expiry_days parameter to your API call to set how long the signing request stays open. The default is 30 days. Expired documents do not consume credits.

Using webhooks to react to signing events

Configure a webhook URL in your API call. eSignature API sends a POST request to your URL on each signing event:

• Document sent
• Document viewed by recipient
• Document signed by a recipient
• Document completed (all parties signed)
• Document declined or expired

Use these events to trigger downstream actions: update a CRM record, send a confirmation email, store the signed document in your database, or unlock the next step in your onboarding flow.

Example multi-role sequential workflow

Step 1: Form filler completes employee details (name, start date, salary)
Step 2: Employee signs the offer letter
Step 3: Hiring manager countersigns
Step 4: HR director receives a CC copy on completion

In your API call, set four recipients with roles form_filler (order 1), signer (order 2), signer (order 3), and cc (no order needed).