PDFHQ logo

Documents

eSignature webhooks and lifecycle

Verified Dropbox Sign callbacks, idempotent delivery, status transitions, delayed downloads and reconciliation of uncertain sends.

Server-side API keys Signed storage uploads

Trusted provider callbacks#

Dropbox Sign sends form-data with a json field. PDFHQ verifies the primary API key HMAC over the event timestamp/type and the Content-Sha256 HMAC over the entire raw JSON. An optional configured app ID must also match.

Endpoint: POST /v1/esign/webhooks/dropbox-sign. Configure this URL only in the Dropbox Sign sandbox API app. Do not expose provider credentials in the browser or customer API requests.

Lifecycle and operational recovery#

Envelope states are draft, dispatching, sent, viewed, partially_signed, all_signed, downloadable, archiving, archived, declined, cancelled, expired, failed and needs_reconciliation. Verified provider callbacks may arrive out of order; updates must not regress a later completed state. Duplicate callback events are persisted once using a unique event key.

Do not download at all_signed: Dropbox Sign may still prepare the file. Wait for the downloadable event. If a provider POST times out, do not create a second signing request until an operator confirms the original provider outcome.

Only the account and API project that created an envelope can read its recipients, archive its output or obtain its download link.

PDFHQ logo

PDF tools and document intelligence. Prepare, understand and work with your documents.

© 2026 PDFHQ. All rights reserved.