Authenticate with the DocuSign CLM API using the appropriate OAuth token with CLM scopes, then call the CLM documents list endpoint to locate the target document by name or external reference ID
Call the document check-out endpoint to lock the document for editing, capturing the checkout token or lock ID returned in the response to be used when checking the document back in
Download the current document version binary using the document content endpoint, make the required modifications to the DOCX or PDF content externally, and prepare the updated file for upload
Call the document check-in endpoint, supplying the checkout token, the updated file content, a version comment describing the changes, and a minor/major version increment flag
Call the document version history endpoint to verify the new version was recorded with the correct version number, author identity, timestamp, and comment, confirming the audit trail is intact
Known gotchas
DocuSign CLM checkout locks prevent concurrent edits, but the lock does not automatically expire in all configurations; a crashed client that fails to check in the document can leave the document locked indefinitely, requiring an administrative force-unlock action
CLM document version numbers follow the CLM system's internal versioning scheme, which may differ from any version numbering embedded in the document's filename or content — do not rely on filename version suffixes as authoritative version identifiers
The CLM API base URL and endpoint paths differ between the DocuSign CLM legacy product and the Spring CM-derived CLM product that DocuSign acquired; accounts on different CLM product lines require different API integration paths even though both are marketed under the DocuSign CLM brand
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