Skip to content

Automation platforms

Send Envelopes From Make

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

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

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.

SettingValue
Method POST
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.

Body content type application/JSON
Body input method JSON string
Body (JSON string)The JSON below.
Body (JSON string)
{
  "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.

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 in test mode with that URL. Subscribe to deliverable.generated, which fires when the signed PDF is ready, and add the make topic so only envelopes from this scenario arrive. The envelope.completed 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.

SettingValue
Method GET
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, 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 for retries and duplicates.