Skip to content

HR and hiring

Send Contractor Agreements From Payroll and EOR Platforms

Send a contractor agreement for signing when Deel or Remote fires a webhook for a new contractor, using an HTTP step in your automation tool.

Global payroll and employer-of-record platforms send webhooks when a worker is created. Route the webhook to an automation tool’s inbound webhook, and let its HTTP step create the envelope that carries the contractor agreement. No SignatureAPI app is needed.

Before you start

Receive the new contractor

Deel. Create a webhook with POST https://api.letsdeel.com/rest/webhooks, with a public HTTPS url and an events array such as contract.created. Call /webhooks/events/types to list the event types. The response includes a signing_key, and each delivery has an x-deel-signature header, an HMAC-SHA256 over the string POST followed by the raw body. Reply 200 within 30 seconds. See the Deel webhooks quickstart.

Remote. Remote lists the events you can subscribe to, with the trigger for each. employment.user_status.initiated fires on employment creation, and employment.employment_agreement.available fires when the employment agreement is ready to sign. See Available webhooks.

Other platforms work the same way: find the event for a new contractor in the platform’s webhook documentation and send it to the tool’s inbound webhook.

Send the envelope

Add an HTTP step after the webhook. Map the contractor’s name and email into recipients[0] and the platform’s contractor id into metadata.contractor_id.

HTTP request step

Settings for the "Contractor agreement" request.

SettingValue
Method POST
URL https://api.signatureapi.com/v1/envelopes
Header X-API-Key: YOUR_API_KEY

Store the key in your tool's secret or credential storage when it has one.

Header Content-Type: application/json
Body (raw JSON)The JSON below.
Body (raw JSON)
{
  "title": "Contractor Agreement - Jane Doe",
  "message": "Please review and sign your contractor agreement.",
  "metadata": {
    "source": "eor",
    "contractor_id": "ctr_1042"
  },
  "topics": [
    "no_code",
    "contractors"
  ],
  "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"
    }
  ]
}

Store the envelope id from the response next to the contractor record. data.envelope_metadata.contractor_id also comes back in every webhook event, and the contractors topic lets an endpoint receive only these envelopes.

Get the result back

Add a webhook endpoint in the Dashboard, in test mode, pointing at a second inbound webhook. Subscribe to deliverable.generated, which fires when the signed PDF is ready, and add the contractors topic. The envelope.completed event comes earlier, while the PDF may still be generating, so use it only to update a status. Anyone who knows the endpoint URL can call it, so read the envelope with your key before you act.

HTTP request step

Settings for the "Completed envelope" request.

SettingValue
Method GET
URL https://api.signatureapi.com/v1/envelopes/eb4cf433-a8af-4161-b37b-7ef57d423e56
Header X-API-Key: YOUR_API_KEY

Store the key in your tool's secret or credential storage when it has one.

Act on the response: deliverable.status is generated, metadata.contractor_id names the contractor, 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. If the platform’s API accepts file uploads for a contractor, attach the signed PDF there. Otherwise store it where your team keeps contracts.