Manage DocuSign embedded signing (recipient view) URL and OAuth session lifecycle, including the 5-minute view-URL and 1-hour JWT token expiry
domain: developers.docusign.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain an OAuth access token via JWT Grant; this token expires after 1 hour and DocuSign does not issue a refresh token for the JWT flow, so long-running services must re-run the JWT assertion rather than expect a refresh token.
Create the envelope with the target recipient flagged as embedded by setting clientUserId on that recipient.
Call createRecipientView (POST /envelopes/{envelopeId}/views/recipient) with the recipient's clientUserId, returnUrl, and authentication method to obtain a one-time signing URL.
Redirect the recipient's browser to the returned URL immediately - it is single-use and expires about 5 minutes after being generated if not opened.
If the recipient doesn't launch the view in time, don't reuse the stale URL - issue a fresh createRecipientView call to generate a new one.
Inspect the event query parameter on your returnUrl callback (e.g., signing_complete, decline, ttl_expired) to detect an expired or abandoned session and trigger regeneration.
Known gotchas
The recipient view URL is one-time-use and expires roughly 5 minutes after issuance - pre-generating URLs for later/batched use will fail.
JWT Grant access tokens expire in 1 hour with no refresh token; server processes must repeat the JWT authentication call rather than relying on token refresh.
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?