Subscribe to Adobe Acrobat Sign webhook events for agreement status changes

Steps

1. Register a publicly reachable HTTPS endpoint that returns HTTP 200 within a reasonable time; Acrobat Sign will disable the webhook if your endpoint fails to respond within 72 hours across retries
2. POST to /api/rest/v6/webhooks with a JSON body specifying name, scope (ACCOUNT, GROUP, or USER), state (ACTIVE), webhookSubscriptionEvents (e.g., AGREEMENT_WORKFLOW_COMPLETED, AGREEMENT_ALL), webhookUrlInfo.url pointing to your endpoint, and resourceType (AGREEMENT)
3. Handle the verification ping: on registration Acrobat Sign sends a GET to your URL with X-AdobeSign-ClientId; respond with 200 and that same client ID in the X-AdobeSign-ClientId response header
4. Parse incoming POST payloads; the payload is JSON with an event field (e.g., AGREEMENT_WORKFLOW_COMPLETED) and nested agreementAssetInfo containing the agreementId and current status
5. Use the agreementId from the payload to call GET /agreements/{agreementId} for full record details, or retrieve the signed document as needed