Implement CLM contract version control: upload, check-out, and check-in document versions via the DocuSign CLM API

Steps

1. 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
2. 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
3. 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
4. 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
5. 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
6. 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