---
title: "Send Envelopes From Make"
description: "Create SignatureAPI envelopes from a Make scenario with the HTTP app, and receive signing events with a Webhooks custom webhook."
canonical: "https://signatureapi.com/docs/integrations/make"
source: "https://signatureapi.com/docs/integrations/make.md"
last_verified_api_version: "1.18.0"
---

# Send Envelopes From Make

Create SignatureAPI envelopes from a Make scenario with the HTTP app, and receive signing events with a Webhooks custom webhook.

_Last verified against API version 1.18.0._

Make calls the SignatureAPI REST API through its own **HTTP** app. No SignatureAPI app is needed: one **Make a request** module creates the envelope, and a **Custom webhook** trigger in a second scenario receives the result.

## Before you start

- A SignatureAPI [test API key](https://signatureapi.com/docs/api/test-mode) (it starts with `key_test_`).
- The document you send, at a URL on a [supported host](https://signatureapi.com/docs/api/resources/documents/url#external-store), or [uploaded to SignatureAPI](https://signatureapi.com/docs/api/resources/uploads/create) first. The examples use a sample PDF.

## Send the envelope

1. **Store the key in a keychain**

   In the **Make a request** module, set **Authentication type** to **API key** and create a keychain in **Credentials**. Enter your key in **Key**, choose **In the header** for **API key placement**, and enter `X-API-Key` as the **API key parameter name**. Make recommends a keychain over the **Headers** field, so the key stays out of the module settings.

2. **Set the request**

   Set **Method** to `POST`, **URL** to `https://api.signatureapi.com/v1/envelopes`, **Body content type** to `application/JSON` and **Body input method** to **JSON string**. Paste the body below and map the recipient's name and email, and your record id, from earlier modules.

3. **Parse the response**

   Set **Parse response** to **Yes**. The response is the new envelope: store its `id` on your record so later events can find it.

Make HTTP request step settings for the "Service agreement" request:

1. **Method**: POST
2. **URL**: `https://api.signatureapi.com/v1/envelopes`

   The API key comes from the setup in the steps above, so the step needs no header row for it.
3. **Body content type**: application/JSON
4. **Body input method**: JSON string
5. **Body (JSON string)**:

   ```json
   {
     "title": "Service Agreement - Jane Doe",
     "message": "Please review and sign the service agreement.",
     "metadata": {
       "source": "make",
       "record_id": "rec_1042"
     },
     "topics": [
       "no_code",
       "make"
     ],
     "documents": [
       {
         "key": "service_agreement",
         "url": "https://pub-9cb75390636c4a8a83a6f76da33d7f45.r2.dev/docs-samples/service-agreement.pdf",
         "format": "pdf",
         "fixed_positions": [
           {
             "place_key": "signer_signature",
             "page": 1,
             "top": 172,
             "left": 210
           }
         ],
         "places": [
           {
             "key": "signer_signature",
             "type": "signature",
             "recipient_key": "signer"
           }
         ]
       }
     ],
     "recipients": [
       {
         "type": "signer",
         "key": "signer",
         "name": "Jane Doe",
         "email": "jane.doe@example.com"
       }
     ]
   }
   ```

Setting names as in the [Make documentation](https://apps.make.com/http).

`data.envelope_metadata.record_id` comes back in every webhook event for this envelope, and the `make` topic lets an endpoint receive only these envelopes.

When you map values into the JSON string, a quote or line break in a mapped value breaks the JSON. Map plain values such as names and emails, or build the body with Make's **Data structure** input method instead.

## Get the result back

1. **Create a custom webhook**

   Start a second scenario with the **Webhooks** app's **Custom webhook** trigger. Save it and copy the URL Make generates.

2. **Register the URL in SignatureAPI**

   In the Dashboard, add a [webhook endpoint](https://signatureapi.com/docs/api/guides/how-to/set-up-webhooks) in test mode with that URL. Subscribe to [`deliverable.generated`](https://signatureapi.com/docs/api/resources/events/deliverable-events#deliverablegenerated), which fires when the signed PDF is ready, and add the `make` topic so only envelopes from this scenario arrive. The [`envelope.completed`](https://signatureapi.com/docs/api/resources/events/envelope-events#envelopecompleted) event comes earlier, while the PDF may still be generating, so use it only to update a status.

3. **Read the envelope before you act**

   The event body tells you which envelope changed, in `data.envelope_id`. Anyone who knows the webhook URL can call it, so read the envelope with your key before you update anything. Add a **Make a request** module with the same keychain, and put the envelope id from the event in the URL:

   Make HTTP request step settings for the "Completed envelope" request:

   1. **Method**: GET
   2. **URL**: `https://api.signatureapi.com/v1/envelopes/eb4cf433-a8af-4161-b37b-7ef57d423e56`

      The API key comes from the setup in the steps above, so the step needs no header row for it.

   Act on the response: `deliverable.status` is `generated`, `metadata.record_id` names your record, and `deliverable.url` downloads the signed PDF. That link expires after an hour, so download the file in the same run. If your account uses [authenticated deliverable URLs](https://signatureapi.com/docs/api/resources/deliverables/object#url), send your API key with the download.

SignatureAPI expects a `2XX` answer and retries a failed delivery for up to 48 hours. A Custom webhook answers `200` once Make accepts the request, so you don't need a **Webhook response** module. The same event can arrive twice: skip it if your record already has the signed PDF. See [Webhooks](https://signatureapi.com/docs/api/webhooks) for retries and duplicates.

## Related

- [Create an envelope](https://signatureapi.com/docs/api/resources/envelopes/create): every field of the request body.
- [Organize with topics and metadata](https://signatureapi.com/docs/api/guides/how-to/organize-topics-metadata).
- [Zapier](https://signatureapi.com/docs/integrations/zapier/http-recipe) and [n8n](https://signatureapi.com/docs/integrations/n8n) use the same request.

### Example: Service agreement

Sent from a Make HTTP module.

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

{
  "title": "Service Agreement - Jane Doe",
  "message": "Please review and sign the service agreement.",
  "metadata": {
    "source": "make",
    "record_id": "rec_1042"
  },
  "topics": [
    "no_code",
    "make"
  ],
  "documents": [
    {
      "key": "service_agreement",
      "url": "https://pub-9cb75390636c4a8a83a6f76da33d7f45.r2.dev/docs-samples/service-agreement.pdf",
      "format": "pdf",
      "fixed_positions": [
        {
          "place_key": "signer_signature",
          "page": 1,
          "top": 172,
          "left": 210
        }
      ],
      "places": [
        {
          "key": "signer_signature",
          "type": "signature",
          "recipient_key": "signer"
        }
      ]
    }
  ],
  "recipients": [
    {
      "type": "signer",
      "key": "signer",
      "name": "Jane Doe",
      "email": "jane.doe@example.com"
    }
  ]
}
```

Response 201 Created:

```json
{
  "id": "eb4cf433-a8af-4161-b37b-7ef57d423e56",
  "title": "Service Agreement - Jane Doe",
  "label": null,
  "message": "Please review and sign the service agreement.",
  "status": "processing",
  "attestation": "none",
  "language": "en",
  "mode": "test",
  "routing": "sequential",
  "timezone": "UTC",
  "timestamp_format": "MM/DD/YYYY HH:mm:ss",
  "snapshot_url": null,
  "branding": {
    "logo": null,
    "accent_color": "#2463EB",
    "email": {
      "footer": null,
      "logo_position": "left",
      "from": "noreply@signatureapi.com"
    }
  },
  "deliverable": {
    "id": "del_6FF89lKNyTNamOJCJd1tLL",
    "envelope_id": "eb4cf433-a8af-4161-b37b-7ef57d423e56",
    "name": null,
    "status": "pending",
    "type": "standard",
    "url": null,
    "password": null,
    "created_at": "2026-11-02T14:03:11.000Z",
    "generated_at": null,
    "timezone": "UTC",
    "language": "en",
    "timestamp_format": "MM/DD/YYYY HH:mm:ss",
    "included_documents": [
      "service_agreement"
    ]
  },
  "metadata": {
    "source": "make",
    "record_id": "rec_1042"
  },
  "sender": {
    "name": "Acme Corp Legal",
    "email": "legal@acme.example",
    "organization": "Acme Corp"
  },
  "captures": {},
  "documents": [
    {
      "id": "doc_HVl3Nj7XzTzX7jN3lVH5vn",
      "envelope_id": "eb4cf433-a8af-4161-b37b-7ef57d423e56",
      "key": "service_agreement",
      "title": null,
      "page_count": 1,
      "url": "https://pub-9cb75390636c4a8a83a6f76da33d7f45.r2.dev/docs-samples/service-agreement.pdf",
      "format": "pdf",
      "fixed_positions": [
        {
          "page": 1,
          "top": 172,
          "left": 210,
          "place_key": "signer_signature"
        }
      ],
      "places": [
        {
          "key": "signer_signature",
          "type": "signature",
          "recipient_key": "signer",
          "height": 60
        }
      ]
    }
  ],
  "recipients": [
    {
      "id": "re_49r1R2jpPDz8hSpP75ZkPp",
      "envelope_id": "eb4cf433-a8af-4161-b37b-7ef57d423e56",
      "type": "signer",
      "key": "signer",
      "email": "jane.doe@example.com",
      "name": "Jane Doe",
      "ceremony": {
        "authentication": [
          {
            "type": "email_link",
            "subject_override": null,
            "message_override": null
          }
        ],
        "embeddable_in": [],
        "redirect_url": null,
        "redirect_delay": 3,
        "url": null,
        "url_variant": "standard"
      },
      "ceremony_creation": "automatic",
      "delivery_type": "email",
      "signature_options": [
        "typed",
        "drawn"
      ],
      "status": "pending",
      "status_updated_at": "2026-11-02T14:03:11.000Z",
      "completed_at": null
    }
  ],
  "topics": [
    "no_code",
    "make"
  ],
  "created_at": "2026-11-02T14:03:11.000Z",
  "completed_at": null
}
```

Response 422 Unprocessable Content:

```json
{
  "type": "https://signatureapi.com/docs/v1/errors/validation-error",
  "title": "Validation Error",
  "status": 422,
  "errors": [
    "recipients[0].email must be a valid email address."
  ]
}
```

Errors that any request can return (authentication, rate limits, server errors) are on the [Errors](https://signatureapi.com/docs/api/errors) and [Authentication](https://signatureapi.com/docs/api/authentication) pages.
