Retrieve DocuSign ID evidence data after a recipient completes identity verification
domain: developers.docusign.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Ensure your OAuth token includes the identity_verification scope in addition to the standard signature scope
After the envelope reaches a signed or completed state, call the ID Evidence API: GET /v2.1/accounts/{accountId}/envelopes/{envelopeId}/recipients/{recipientId}/id_evidence
Parse the response, which contains the verificationStatus, identityVerificationWorkflowId, and an evidenceResourceToken that grants access to the detailed evidence payload
Use the evidenceResourceToken to call the IDEvidence resource endpoint to retrieve structured data including extracted name, date of birth, document type, issuing country, and a photograph if captured
Store the evidence payload alongside the signed document in your records management system to satisfy regulatory audit requirements
Known gotchas
The evidenceResourceToken is short-lived; retrieve and store the full evidence payload promptly after obtaining the token — do not store only the token
Evidence data availability depends on the IDV workflow used; some workflows return only a pass/fail verification status without raw document data
The ID Evidence API is a separate API product with its own base URL and versioning; do not assume it shares the eSignature REST API base URL
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?