Skip to content

Signing Requests API

The current signing-request flow is powered by the create-signing-request edge function.

Create Request

http
POST /functions/v1/create-signing-request

Example Payload

json
{
  "documentId": "doc_123",
  "signerName": "Jane Doe",
  "signerEmail": "jane@example.com",
  "routingMode": "parallel"
}

Common Fields

FieldTypeNotes
documentIdstringSource document identifier
signerNamestringRecipient display name
signerEmailstringRecipient email
routingModestringparallel or sequential
signingOrdernumberUsed for sequential chains
requestGroupIdstringShared group id for multi-signer workflows
webhookUrlstringOptional license-linked completion destination

Supported Operations

The frontend/service layer currently supports:

  • create
  • bulk create
  • resend
  • cancel
  • duplicate
  • reopen

Response Shape

Typical response data includes:

  • token
  • signing URL
  • request/session identifiers
  • source PDF URL when available

Notes

  • email delivery depends on Resend configuration
  • sequential activation depends on request metadata plus completion handling

Built for product, engineering, and operations teams shipping PDF signing flows.