Authenticate to the DocuSign CLM API using OAuth 2.0 (JWT grant or authorization code flow) targeting the CLM API scope; obtain an access token from the DocuSign identity server
Upload a new contract document to CLM by POSTing the file binary to the CLM Content API document upload endpoint; record the returned document ID
Check out the document for editing by calling the check-out endpoint with the document ID; this locks the document in CLM to prevent concurrent edits and returns a checkout token
Download the document, apply tracked-change edits in a Word processor (DocuSign CLM does not support in-platform redlining; edits must be made externally in Word using Track Changes), then re-upload the modified DOCX
Check in the edited document using the check-in endpoint, passing the checkout token and the new file binary; CLM creates a new version and records the change history with the actor and timestamp
Use the document compare capability (UI-based) or retrieve version metadata via the CLM API to show version diffs to reviewers; the API returns version list metadata including version number, actor, and timestamp for each version
Known gotchas
DocuSign CLM has no native in-platform redlining API — the tracked-changes workflow requires downloading to Word, editing, and re-uploading; plan for this round-trip in your user-facing workflow design
A document remains locked to the user who checked it out until it is checked back in or the checkout is explicitly cancelled; failing to handle this in error paths leaves documents permanently locked
CLM API base URLs differ by environment (demo vs. production) and by account region; always derive the base URL from the account info endpoint rather than hard-coding a regional URL
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp