Niches · Contracts, proposals & e-signatures

Know when each signer has signed

Two or three companies' docs show a full fit.

2companies, full fit
8companies, fit with a limit
10companies carry the tag
19share of the category's work
6first-hand accounts

What counts as done

A per-signer status (sent, viewed, signed, declined), delivered by a signed webhook or by a single lookup call, with retried deliveries deduplicable.

Measured, for our own tests: the status matches the provider's dashboard, and the webhook arrives within 60 seconds of the signature. No docs we read state these figures, so they don't count against a listing here.

How agents ask for it: has the client signed yet, tell me when the contract is signed, who still hasn't signed, find the envelope for this deal

Does the job 2

The docs show it meets the test above, and nothing we read says otherwise.

ListingWhy
BoldSign BB
Syncfusion, Inc.
Viewed, Signed, Declined, Reassigned and Completed events per recipient, retried at 1, 15 and 45 minutes then hourly, with a unique event id in the metadata and an X-BoldSign-Signature HMAC to verify. List documents also filters by status. source
Youtrust BB
Youtrust SAS
signer.notified, signer.done, signer.declined and approver events per person, x-yousign-signature-256 HMAC, x-yousign-retry count and an event_id, retried up to eight times with exponential backoff when auto_retry is set. source

Does the job, with a limit 8

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
Adobe Acrobat Sign D
Adobe Inc.
Webhooks retry 15 times over 72 hours and then disable themselves, losing later events. There is no delivery id header or payload HMAC, only an X-ADOBESIGN-CLIENTID echo, and identical GETs past three a minute return 429. source
Documenso C
Documenso, Inc.
document.opened, document.recipient.completed, document.rejected and document.completed exist, but acc-15 (open) shows recipient.completed not firing for direct-link signers. Retries depend on the background-job provider with no schedule, and the secret travels in a plain header, no HMAC. source
DocuSeal B
DocuSeal, LLC
form.viewed, form.started, form.completed and form.declined fire per submitter; failures are retried for 48 hours at 2^attempt minutes. No delivery id or payload HMAC is documented, and acc-11's late retries were closed by redirecting to support. source
Docusign B
Docusign, Inc.
Connect and eventNotification take recipientEvents per signer and includeHMAC. Docusign asks for no more than one status poll per 15 minutes, the retry schedule sits in the script-rendered Developer Center, acc-24's Connect events never arrived and acc-25's search_text stopped matching. source
Dropbox Sign B
Dropbox, Inc.
signature_request_viewed, _signed, _declined and _all_signed events, retried with exponential backoff for about three days, Content-Sha256 HMAC over the payload. No delivery id is named and the docs say the same event can arrive twice; ten consecutive failures clear the callback URL. source
PandaDoc B
PandaDoc
recipient_completed and document_state_changed events carry X-PandaDoc-Webhook-Event-Id and an HMAC-SHA256 signature, but PandaDoc sends each webhook once and does not retry; resends are manual from the dashboard. source
airSlate SignNow B
airSlate, Inc.
document.fieldinvite.sent, .signed and .decline fire per invite, with an HMAC header over the body and retry_count 1 to 10 on 5xx. Views come only as document.open per document, no delivery id is named, and the docs tell callers to build their own dedupe key. source
SignWell B
Docsketch, LLC (DBA SignWell)
document_viewed and document_signed fire per recipient, plus declined and completed. No retry schedule or delivery id is documented, the event hash does not cover the payload, and List Documents is absent from the public reference. source

What stops agents finishing

  • event not sent for one signing path (direct link)
  • webhook retry policy undocumented or not retried
  • status polling capped by the provider (Docusign asks for no more than once every 15 minutes)

Around it

Before: e-signatures.send-from-template, e-signatures.generate-and-send. After: e-signatures.fetch-signed-file, notifications.send, crm.update-deal.

Where this comes from

Weight 19 of 100 in Contracts, proposals & e-signatures: 6 of 31 accounts: DocuSeal webhook retries and signer filters, Documenso missing per-recipient event, Docusign Connect not arriving and text search breaking, and the provider-switched webhook build

The same as data: /api/v1/use-cases/e-signatures.track-status.json, or the MCP tool get_use_case with id e-signatures.track-status. Other jobs in this category: /api/v1/niches?category=e-signatures.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.