# Know when each signer has signed

> Know when each signer has signed: 2 companies fully do it, 8 with a limit, 10 carry the tag. Every listing in Contracts, proposals & e-signatures with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/e-signatures.track-status/
- Markdown: https://www.anchorterminal.com/niches/e-signatures.track-status/index.md (~1,350 tokens)
- Slim: https://www.anchorterminal.com/niches/e-signatures.track-status/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/e-signatures.track-status/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Two or three companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 2 | 8 | 10 | 19 | 6 |

## 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.

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

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

- **BoldSign (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.
- **Youtrust (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.

## Does the job, with a limit

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.

- **Adobe Acrobat Sign (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.
- **Documenso (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.
- **DocuSeal (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.
- **Docusign (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.
- **Dropbox Sign (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.
- **PandaDoc (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.
- **airSlate SignNow (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.
- **SignWell (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.

## 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

As data: https://www.anchorterminal.com/api/v1/use-cases/e-signatures.track-status.json, or the MCP tool get_use_case with id e-signatures.track-status. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
