DocuSign CLM

Record your DocuSign CLM connection as digital signature evidence. Automated collection is not available for this provider yet.

Connect with an API token

1. In DocuSign CLM:

   1. Log in to your Docusign developer account and open the Apps and Keys page (Docusign Admin).
   2. Add a new app: in the Add API Integration Key dialog, give the app a short descriptive name and select ADD. The app is assigned an integration key (GUID) that cannot be changed, and apps cannot be deleted.
   3. On the list of apps and integration keys, find the app and select EDIT from its ACTIONS menu.
   4. In the User Application section, select Yes (the application can securely store a client secret) for Confidential Authorization Code Grant.
   5. Select ADD SECRET KEY and copy the generated secret key immediately; it is masked and cannot be revealed again after the settings are saved.
   6. Select ADD URI, enter the redirect URI, and select SAVE.
   7. Request an access token with Confidential Authorization Code Grant, asking for the CLM read scope in the request URL, as in Docusign's developer-account example: https://account-d.docusign.com/oauth/auth?response_type=code&scope=signature%20spring_read&client_id=&lt;integration key>&redirect_uri=<redirect URI>.
   8. Request only spring_read (read access to all CLM objects, including downloading documents); do not request spring_write. With JWT Grant the impersonation scope is also required.

   Where to find the other values:

   • Account / Org / Workspace (optional): You can find your API Account ID on the Apps and Keys page.

   DocuSign CLM shows the secret only once, so copy it before you leave the page.

   DocuSign CLM's public documentation does not cover every step.

   CLM API access is only available to Docusign CLM customers with a production account (contact Docusign Sales); you need an eSignature developer account plus a CLM account. CLM has no static API token: the access token comes from a Docusign OAuth2 flow (Confidential/Public Authorization Code, Implicit or JWT Grant) with a CLM scope (spring_read, spring_write or content). The label of the button that opens the Add API Integration Key dialog sits in an embedded element that could not be read. The CLM-specific API base URLs (separate from the eSignature base_uri) were not sourced. The Docusign pages render in the browser; their content was read from the site's own Gatsby page-data JSON. Verification 2026-10-07: the token-exchange page (confidential-authcode-get-token) could not be read, so the production OAuth host and the code-for-token exchange are not spelled out here; the /oauth/userinfo account_id claim was removed as unsourced.

   Source: developers.docusign.com, developers.docusign.com, developers.docusign.com, developers.docusign.com, developers.docusign.com, checked 2026-10-07.

2. On Compliance › Connectors, open DocuSign CLM, click Connect, choose API token and fill in:

   Field	What to enter
   API token / Personal access token	Required. Stored encrypted and never shown again.
   Base URL (optional)	—
   Account / Org / Workspace (optional)	—

3. Click Connect with token.

Frameworks

No automated compliance test reads DocuSign CLM yet, so no framework lists it. How connectors provide evidence for frameworks: Frameworks and connectors.

Related

• Digital Signature connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks