Trigger an offer-letter e-signature workflow via the DocuSign eSignature API after an ATS offer is approved
domain: developers.docusign.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create an envelope from an offer-letter template via the envelopes create endpoint, populating the candidate as a recipient/role
Include an eventNotification block at send time to get status callbacks for that specific envelope
Alternatively, configure account-level DocuSign Connect to receive notifications for envelopes sent by any user on the account
Expose an HTTPS URL reachable from the public internet for DocuSign to call back
Send the envelope to start the signing request
Handle the resulting webhook payload reporting envelope and recipient status changes, including completion
Known gotchas
Per-envelope eventNotification and account-level Connect are two distinct webhook mechanisms with different scope — choose deliberately
Making API calls against Connect configuration endpoints requires the caller to be an account administrator
Envelope creation and status transitions are asynchronous, so status must be read from a webhook or a follow-up poll rather than assumed from the create response
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?