Webhooks

How Webhooks Work

You configure a webhook URL in Documenso
When an event occurs, Documenso sends an HTTP POST to your URL
Your application processes the event and responds with 200 OK

Documenso supports webhook events for the full document lifecycle (created, sent, opened, signed, completed, rejected, cancelled), recipient-level events (recipient completed, reminder sent, recipient expired), and template events (created, updated, deleted, used).

Getting Started

Setup

Configure webhook endpoints.

Events

Available webhook event types.

Verification

Verify webhook signatures for security.

Example Payload

{
  "event": "DOCUMENT_COMPLETED",
  "payload": {
    "id": 123,
    "envelopeId": "envelope_abcdefhiklmnorst",
    "title": "Contract",
    "status": "COMPLETED",
    "completedAt": "2024-01-15T10:30:00.000Z",
    "recipients": [
      {
        "id": 1,
        "envelopeId": "envelope_abcdefhiklmnorst",
        "email": "signer@example.com",
        "signingStatus": "SIGNED"
      }
    ]
  },
  "createdAt": "2024-01-15T10:30:00.000Z",
  "webhookEndpoint": "https://your-endpoint.com/webhook"
}

payload.id is the legacy numeric v1 ID. Use payload.envelopeId as the canonical v2 identifier. Each recipient repeats envelopeId as the reliable parent link because the legacy documentId and templateId fields depend on the parent envelope type, leaving one of them null.