Flowgrammer

Dropbox Sign Callback Verification Pack

Original Dropbox Sign callback pack with event_hash vectors, exact ack tests, and eighteen fictional cases.

Download the callback verification pack (ZIP)

Download this pack when Dropbox Sign requests already go out and you need to prove callback ack and event_hash before SignatureEvidence accepts a row. The pack implements the Dropbox Sign E-Signature Automation adapter and the published E-Signature Automation control plane. It includes fiction event_hash vectors, exact ack-string tests, eighteen cases, and a forbidden-downstream sheet.

Read the paired guide first: Dropbox Sign E-Signature Automation. Keep the shared Signing Workflow Requirements Workbook nearby for the field list. If you already verify DocuSign Connect, keep the published DocuSign E-Signature Automation page for that HMAC. The algorithms are not interchangeable.

Download the callback verification pack (ZIP)

The ZIP includes event_hash vectors, ack-string tests, JSON event files, setup notes, a timing matrix, and SX01 through SX12 plus SX-DBX-01 through SX-DBX-06. Samples stay fictional on 9 September 2026. No live Dropbox Sign tenant is included, and this is not a Marketplace listing.

What you get

  • HMAC-SHA256 hex vectors for event_hash over event_time plus event_type
  • Exact ack tests for Hello API Event Received
  • Multipart json parse failures
  • Account versus app callback scope
  • signature_request_all_signed versus signature_request_downloadable
  • Fast ACK with queued-work notes
  • An idempotency table for retried events
  • Forbidden-downstream rules for payment, bank-detail change, accounting, auto-renew, and auto-terminate
  • Eighteen fictional Cedar & Quay cases on DOC-CQ-SIGN-014

Keep these jobs separate

A completed signature request is not Dropbox Document Approval DecisionEvidence. This pack covers the eSignature callback adapter. Recipient signing and vendor-hosted actions may implement a vendor gate. Broader Dropbox approval products exist. Those surfaces do not automatically become Flowgrammer Document Approval DecisionEvidence. Use the published Dropbox document approval workflow when an org decision is required on a Dropbox file. Use the published Document Approval Workflow when the org needs a named approve, reject, or request-changes decision. This pack does not run IDP or OCR. Use invoice processing automation or the contract tracker when money or renewal is the actual job.

If you still need the shared signing model, start with E-Signature Automation. If you still need to choose a first workflow, start with Document Processing Automation.

How to start

  1. Read README.md, then markdown/setup.md.
  2. Walk csv/event-hash-vectors.csv and csv/ack-string-tests.csv.
  3. Confirm HV01 passes and HV04 fails when time and type are swapped.
  4. Confirm the exact ack string passes and an empty or JSON body fails.
  5. Walk SX01 through SX12, then SX-DBX-01 through SX-DBX-06.
  6. Keep the paired Dropbox Sign E-Signature Automation guide nearby.

If callback enablement, API keys, or the event log are still unclear, start with an AI Success Audit. If they are named, book a fit call to scope an AI Automation Systems build.

Book an AI Success Audit call