How E-Signatures Work

The signing flow

1. You create a signable document via the API
2. ZipZign renders the PDF and emails each signer a unique link
3. Each signer opens their link → sees the PDF + a signature UI
4. Signer draws, types, or uploads their signature and clicks Sign
5. ZipZign records the signature, IP, user agent, timestamp, and consent
6. Once all signers have signed, the document status moves to all_signed → complete
7. The final PDF (with embedded signatures) is available at pdfUrl

What signers see

Signers access a mobile-friendly hosted page — no account required. They can:

• Read the full PDF document
• Draw a signature using a touchpad or mouse
• Type their name and select a signature style
• Upload an image of their signature

Max signers

Up to 6 signers per document.

Signing via API (for automated flows)

For programmatic signing (e.g., testing or internal flows where you control the signer):

curl -X POST https://zipzign.com/api/documents/doc_abc123/sign \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "signerId": "sgn_xyz789",
    "consentGiven": true
  }'

consentGiven: true is required. This records that the signer explicitly consented to e-signing under ESIGN/UETA.

Signature order

By default, all signers receive their invitation simultaneously. If you need sequential signing (signer 2 only gets their invite after signer 1 signs), contact support — sequential mode is available on Pro and Unlimited plans.

Signer status

Query document status to see each signer's progress:

{
  "signers": [
    {
      "id": "sgn_1",
      "name": "Alice",
      "email": "alice@example.com",
      "status": "signed",
      "signedAt": "2026-04-15T15:00:00Z"
    },
    {
      "id": "sgn_2",
      "name": "Bob",
      "email": "bob@example.com",
      "status": "pending"
    }
  ]
}

The signed PDF

Once complete, the PDF at pdfUrl includes:

• The original document content
• Signature blocks for each signer (name, signature image, timestamp, IP)
• A footer with the document ID and verification URL

Updated on: 16/04/2026