Capture standalone clickwrap 'I agree' consent using the DocuSign Click API outside a full envelope signing ceremony
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 a clickwrap (an elastic template holding the agreement terms/display settings) via the Click API's ClickWraps create operation.
Publish an active version of the clickwrap using the create-clickwrap-version operation so it has a live, servable version end users can agree to.
Embed the clickwrap in your site/app using Click's client-side JavaScript snippet, passing the clickwrapId and a clientUserId for the specific end user; the snippet renders the terms and an Agree control directly in your page.
When the user clicks Agree, the Click service records the consent event server-side automatically; retrieve captured agreement/consent records for a given clickwrap and user via the ClickWraps resource's get-clickwrap-agreements operation.
For a fully server-driven (non-embedded) flow, send the clickwrap's hosted URL to the end user directly instead of embedding the JS snippet, then still retrieve consent status afterward via get-clickwrap-agreements.
Use the get-agreement-pdf operation to fetch a PDF record of a specific captured agreement for audit/compliance retention, independent of any DocuSign envelope.
Known gotchas
Click consent events are entirely separate from eSignature envelopes — there is no envelopeId involved; agreements are tracked by clickwrapId + clientUserId, so don't try to correlate them through the Envelopes resource.
A clickwrap must have a published/active version before it can capture agreements — creating a clickwrap alone in draft state is not enough.
The Click API runs on its own base path distinct from the eSignature REST API path — using the eSignature account base URI directly for Click calls will fail.
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?