---
title: "SignatureAPI Docs"
description: "Add electronic signatures to your app with the SignatureAPI REST API: send envelopes, embed signing on web and mobile, and get webhook events."
canonical: "https://signatureapi.com/docs/api/welcome"
source: "https://signatureapi.com/docs/api/welcome.md"
last_verified_api_version: "1.18.0"
last_modified: "2026-11-18T18:19:06Z"
---

# SignatureAPI Docs

Add electronic signatures to your app with the SignatureAPI REST API: send envelopes, embed signing on web and mobile, and get webhook events.

_Last verified against API version 1.18.0._

Integrate electronic signatures into your apps and workflows with SignatureAPI.

## Get started

- [API Quickstart](https://signatureapi.com/docs/api/guides/quickstart): Create your first envelope and send it for signature using the REST API.

- [Power Automate Quickstart](https://signatureapi.com/docs/integrations/power-automate/guides/quickstart): Build your first no-code signing workflow in Power Automate.

## What you can do

- [Send documents for signature](https://signatureapi.com/docs/api/resources/envelopes/create): Send to multiple signers in parallel or sequential order. Track every envelope from creation to completion.

- [Generate documents from templates](https://signatureapi.com/docs/api/resources/documents/templates): Fill templates with dynamic data to produce ready-to-sign documents.

- [Collect information from signers](https://signatureapi.com/docs/api/resources/places/text-input): Add input fields, checkboxes, and dropdowns to capture data during signing.

- [Embed signing in your app](https://signatureapi.com/docs/embedded/introduction): Embed the signing experience in your web app or in your iOS, Android, or React Native app.

- [Automate with Power Automate](https://signatureapi.com/docs/integrations/power-automate/getting-started): Build no-code signing workflows connected to 1,000+ apps.

- [Get notified via webhooks](https://signatureapi.com/docs/api/webhooks): Receive real-time updates when envelopes are signed, completed, or canceled.

[See all capabilities](https://signatureapi.com/docs/api/can_i)

## How it works

Your backend creates envelopes with the API. Each recipient signs in a ceremony, from the signing email or embedded in your app. Webhooks tell your backend when something changes.

**How SignatureAPI fits in your stack**

Parts:

- **Your backend** (Your systems): Holds the API key and creates envelopes.
- **Webhook endpoint** (Your systems): Receives events and verifies their signatures.
- **API** (SignatureAPI): Checks the API key in X-API-Key and validates each request.
- **Envelope** (SignatureAPI): Holds the documents and recipients and moves through its lifecycle.
- **Event** (SignatureAPI): Records each status change of an envelope, recipient or deliverable.
- **Ceremony** (Your recipients): Opened from the signing email or embedded in your app.

Connections:

- Your backend to API: HTTPS requests
- API to Envelope: creates
- Envelope to Ceremony: signing link
- Envelope to Event: status changes
- Event to Webhook endpoint: webhooks

1. **Create an envelope**

   An [envelope](https://signatureapi.com/docs/api/resources/envelopes/object) holds your [documents](https://signatureapi.com/docs/api/resources/documents/object) and [recipients](https://signatureapi.com/docs/api/resources/recipients/object). Add documents directly as PDFs or generate them from [templates](https://signatureapi.com/docs/api/resources/documents/templates).

   ### Example: Minimal

   A PDF with two signers.

   ```http
   POST /v1/envelopes HTTP/1.1
   Host: api.signatureapi.com
   X-API-Key: YOUR_API_KEY
   Content-Type: application/json

   {
     "title": "Service Agreement",
     "message": "Please review the agreement and provide your signature.",
     "routing": "parallel",
     "documents": [
       {
         "key": "service_agreement",
         "title": "Service Agreement",
         "url": "https://pub-9cb75390636c4a8a83a6f76da33d7f45.r2.dev/docs-samples/acme-service-agreement.pdf",
         "format": "pdf",
         "places": [
           {
             "key": "client_signs_here",
             "type": "signature",
             "recipient_key": "client"
           },
           {
             "key": "provider_signs_here",
             "type": "signature",
             "recipient_key": "provider"
           }
         ]
       }
     ],
     "recipients": [
       {
         "type": "signer",
         "key": "client",
         "name": "Jane Doe",
         "email": "jane.doe@example.com"
       },
       {
         "type": "signer",
         "key": "provider",
         "name": "John Smith",
         "email": "john.smith@example.com"
       }
     ]
   }
   ```

   ### Example: Full

   A DOCX template with merge data, branding, an approver and email code authentication.

   ```http
   POST /v1/envelopes HTTP/1.1
   Host: api.signatureapi.com
   X-API-Key: YOUR_API_KEY
   Content-Type: application/json

   {
     "title": "Offer Letter",
     "label": "Offer Letter for Maria Garcia",
     "routing": "sequential",
     "message": "Welcome to Acme Corp! Please review and sign your offer letter.",
     "topics": [
       "hr",
       "onboarding"
     ],
     "metadata": {
       "candidate_ref": "hr-2210"
     },
     "branding": {
       "logo": "https://api.signatureapi.com/v1/uploads/upl_42NTdNnkg6dGLx8jR1X1wm",
       "accent_color": "#9810fa",
       "email": {
         "footer": "**Confidential:** this email is intended only for the named recipient.",
         "logo_position": "left"
       }
     },
     "timezone": "America/New_York",
     "documents": [
       {
         "key": "offer_letter",
         "title": "Offer Letter",
         "url": "https://pub-9cb75390636c4a8a83a6f76da33d7f45.r2.dev/docs-samples/acme-offer-letter-template.docx",
         "format": "docx",
         "data": {
           "candidateName": "Maria Garcia",
           "position": "Product Designer",
           "startDate": "December 1, 2026",
           "salary": "$92,000"
         },
         "places": [
           {
             "key": "candidate_signs_here",
             "type": "signature",
             "recipient_key": "candidate",
             "height": 60
           }
         ]
       }
     ],
     "recipients": [
       {
         "type": "approver",
         "key": "hiring_manager",
         "name": "Alex Chen",
         "email": "alex.chen@example.com"
       },
       {
         "type": "signer",
         "key": "candidate",
         "name": "Maria Garcia",
         "email": "maria.garcia@example.com",
         "signature_options": [
           "typed",
           "drawn"
         ],
         "delivery_type": "email",
         "ceremony": {
           "authentication": [
             {
               "type": "email_code"
             }
           ],
           "redirect_url": "https://acme.example/welcome",
           "embeddable_in": [],
           "url_variant": "standard"
         }
       }
     ],
     "deliverable": {
       "type": "standard",
       "language": "en",
       "timezone": "America/New_York",
       "timestamp_format": "MM/DD/YYYY HH:mm:ss"
     }
   }
   ```

2. **Recipients receive a signing link**

   Each recipient gets a link to review and sign. You can control the [signing order](https://signatureapi.com/docs/api/resources/envelopes/routing) and [authenticate recipients](https://signatureapi.com/docs/api/resources/ceremonies/authentication/overview) before they access the documents.

   ![Signing request email naming the sender and the envelope title, with a View and Sign button and the sender's message](https://signatureapi.com/docs/api/resources/ceremonies/authentication/email-example.webp)

   *Signing request email*

3. **Recipients sign during a ceremony**

   A [ceremony](https://signatureapi.com/docs/api/resources/ceremonies/object) is the guided signing session where recipients review documents and complete their actions.

   ![Signing ceremony with the document open, the test-mode notice at the top of the page, and the Start button](https://signatureapi.com/docs/images/quickstart-ceremony.webp)

   *Signing ceremony*

4. **Retrieve the signed deliverable**

   After all recipients complete their actions, SignatureAPI generates a [deliverable](https://signatureapi.com/docs/api/resources/deliverables/object) containing the signed documents and an audit log.

   ![Sample audit log with the envelope details at the top, the list of events, and the agreed text under each consent event](https://signatureapi.com/docs/images/audit-log-events.webp)

   *Audit log, first page*

## Explore

- [Concepts](https://signatureapi.com/docs/api/concepts): Learn the core building blocks: envelopes, documents, recipients, ceremonies, and deliverables.

- [API Overview](https://signatureapi.com/docs/api/overview): Endpoints, authentication, test mode, pagination, and error handling.

- [API Playground](https://signatureapi.com/docs/api/playground): Try the API directly in your browser.

- [Postman Collection](https://signatureapi.com/docs/api/postman): Import our Postman collection and start exploring.

- [Embedded Signing](https://signatureapi.com/docs/embedded/introduction): Integrate the signing experience into your web or mobile app.

- [Can I ___?](https://signatureapi.com/docs/api/can_i): Quick answers to common questions about SignatureAPI capabilities.
