Implement a DocuSign eSignature workflow with a custom authentication SMS OTP step using the Identity Verification (IDV) configuration API
domain: docusign.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
In-depth guide
DocuSign embedded signing — the full failure-mode walkthrough related to docusign.com, checked against official docs, with linked verified routes.
Steps
Call GET /accounts/{accountId}/identity_verification to enumerate the identity verification workflows configured for the account and locate the SMS OTP workflow configuration ID
Create an envelope via POST /envelopes, and within the recipients array for each signer include an identityVerification object referencing the SMS OTP workflow ID and supplying the signer's phone number in the inputOptions array
Set the requireIdLookup flag to false (SMS OTP is handled by the IDV step, not the legacy phone authentication) and ensure signerMustHaveAccount is false if anonymous signing is intended
Monitor the envelope via Connect webhook; the signer will complete the SMS OTP challenge within the DocuSign signing ceremony before being presented with the document, with the identity event recorded in the envelope audit trail
After completion, call GET /envelopes/{envelopeId}/recipients to inspect the idCheckInformationInput element and verify the identity verification outcome is recorded as passed before accepting the signed document as legally valid
Known gotchas
SMS OTP IDV is an add-on feature that must be provisioned on the DocuSign account before the workflow ID will appear in the identity_verification list; attempting to reference an IDV workflow ID that is not provisioned results in a recipient validation error at envelope creation
The phone number supplied in the inputOptions must be in E.164 format; local or national format phone numbers may pass envelope creation validation but fail at the signing ceremony when the OTP SMS cannot be delivered
IDV outcome data is stored in the envelope audit trail and is retrievable via the envelope audit events endpoint, but it is not included in the standard envelope completed webhook payload — a separate API call is required to confirm the IDV result programmatically
Give your agent this knowledge — and 15,600+ 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?