Trigger a DocuSign Remote Online Notarization (RON) session via the Notary API
domain: developers.docusign.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm that RON is enabled for your DocuSign account and that a notary is provisioned; the Notary API is an add-on to the eSignature plan
Create the envelope using the eSignature REST API as normal, but add a notary recipient to the envelope using the notary role type; set identity verification as required for the notary session
Add a notaryJournal object to the envelope recipient definition to specify the notarization type (e.g., RON) and any required acknowledgment text
Send the envelope; DocuSign will coordinate the live two-way audio-visual session within the browser — no additional plugin or download is needed for participants
After the session, the tamper-evident electronic journal, audio-visual recording, and audit trail are stored within the DocuSign platform; retrieve the notarized document and evidence package via the standard envelope document download endpoints
Known gotchas
RON legality is state-specific in the US; verify that the state where the notary is commissioned and the state where the document originates both permit remote online notarization
The notary recipient must be a registered DocuSign Notary user before being added programmatically; you cannot add an arbitrary email address as a notary recipient
RON sessions generate additional billable charges per transaction beyond the base eSignature plan; confirm pricing before automating high-volume notarization workflows
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?