Skip to main content
The Signature Requests API lets you build complete eSignature workflows — from creating and sending requests to tracking signer progress and downloading signed documents.

​
Key concepts

  • Signature Request — a document sent to one or more signers for legally-binding electronic signatures.
  • Signer — a recipient who must review and sign the document. Each signer receives a unique signing link.
  • Signing Link — a URL that opens the hosted signing experience for a specific signer (redirect flows).
  • Signing Session — a short-lived sign_url for embedding the signing experience inline with the Embed Signing SDK.
  • Template — a reusable document with pre-defined signature fields. Use Send from Template to create requests without re-uploading files each time.

​
Typical workflow

  1. Send a signature request with documents and signer details (or use a template).
  2. Deliver signing to each signer — use Create Signing Session for embedded signing, or Get Signing Link for redirect flows.
  3. Monitor the request status via the Get Signature Request endpoint or webhooks.
  4. Download the signed agreement, Certificate of Completion (CoC), or merged PDF once all signers have completed.

​
Available endpoints

Get Signature Request

Returns the information of the signature request.

Update Signature Request

Update the due date of an existing signature request.

Send Signature Request

Creates and sends a new signature request with the submitted documents.

Send Signature Request from Template

Creates and sends a new signature request from a template with the submitted template data.

Get Signing Link

Returns a hosted signing URL for redirect flows.

Create Signing Session

Returns a short-lived sign_url for the Embed Signing SDK.

Send Reminder Emails

Send reminder emails to signers who still need to sign.

Cancel Signature Request

Cancel a signature request.

Get Signature Request File

Obtain agreement, CoC, or merged PDF via signed URL or binary response.