> You are reading the Docusign Developer Documentation. For clean Markdown of any page, append .md to the page URL.
>
> Documentation indexes by section:
> - APIs and SDKs: https://docusign.docs.buildwithfern.com/docs/llms.txt
> - Platform 101: https://docusign.docs.buildwithfern.com/platform/llms.txt
> - Extension Apps: https://docusign.docs.buildwithfern.com/extension-apps/llms.txt
> - Docusign CLI: https://docusign.docs.buildwithfern.com/docusign-cli/llms.txt
>
> Authentication (OAuth, JWT Grant, M2M): https://docusign.docs.buildwithfern.com/platform/auth
> Webhooks and Connect: https://docusign.docs.buildwithfern.com/platform/webhooks
>
> OpenAPI specifications: https://docusign.docs.buildwithfern.com/openapi.json
> MCP server: https://docusign.docs.buildwithfern.com/_mcp/server

# CLM API 101

> **Warning**
>
> Developing with the CLM API is only available for CLM customers with a production account. To purchase a plan to gain access to the CLM API, contact [Docusign Sales](https://www.docusign.com/contact-sales).

The Docusign CLM API enables developers to interact with Docusign CLM documents, data, and services. Most objects and services available in the Docusign CLM web application are supported in the API. Users and groups are managed through [Docusign Admin](https://www.docusign.com/products/admin). See [Object API](/docs/clm-api/clm101/object-api) for more information.

For additional issues or requests, visit the [Docusign Support Center](https://support.docusign.com).

The Docusign CLM API contains the following logical sub-APIs for working programmatically with Docusign CLM:

* [Object API](/docs/clm-api/clm101/object-api): API methods that create, read, update, and delete (CRUD) Docusign CLM objects, such as folders.
* [Task API](/docs/clm-api/clm101/task-api): API methods that expose Docusign CLM services that are invoked as asynchronous tasks, such as zipping files or running searches.
* [Content API](/docs/clm-api/clm101/content-api): API methods for uploading, downloading, and versioning documents in Docusign CLM.

## Base URLs

All API URLs use the following format:

```text
https://[base url]/[version]/[Docusign Account Id]/[resource identifier]
```

Docusign CLM is distributed across several data centers, and the base URLs for the Object, Task, and Content APIs are data center–specific. You can determine the data center associated with an account by looking at the subdomain of the URL after you log in to the Docusign CLM web application (for example, na11 or s1.us). Content API URLs are properties of the document and folder objects and are discoverable at run time.

You can also get your account-related URLs, including the base CLM API URLs, by making a GET request to these endpoints:

**UAT**: `https://authuat.springcm.com/api/v2/{Docusign API Account ID}/account`

**Production**: `https://auth.springcm.com/api/v2/{Docusign API Account ID}/account`

To find your Docusign API Account ID, log in to your eSignature account and select **Admin** from the top menu, then select **Apps and Keys** from the left navigation. Copy your **API Account ID** value.

**Note**: Similar to endpoints for resources, these endpoints require:

* CLM to be enabled for your account.
* A valid access token in the authorization header. You must request the `springcm_read` scope when you request the access token. See [Authentication](/docs/clm-api/clm101/auth) for details.

### Production endpoints

|                                     |              |
| ----------------------------------- | ------------ |
| **API**                             | **Endpoint** |
| **Production Object API**           | ,            |
| **Production Task API**             | ,            |
| **Production Content Upload API**   | ,            |
| **Production Content Download API** | ,            |

### UAT endpoints

|                              |              |
| ---------------------------- | ------------ |
| **API**                      | **Endpoint** |
| **UAT Object API**           | ,            |
| **UAT Task API**             | ,            |
| **UAT Content Upload API**   | ,            |
| **UAT Content Download API** | ,            |

## Request and response formats

The Docusign CLM Object and Task APIs support JSON for all requests and responses. The Content API by default will download documents in the native format in which they were uploaded. For certain document types, Docusign CLM will also maintain a copy of the document in additional formats such as *.PDF*, *.PNG*, or *.TXT*. See the [Content API reference](/docs/clm-api/reference/Content) for more information.

## Places to start

Start learning about developing with the CLM API:

* [Learn how to authenticate](/docs/clm-api/clm101/auth) with the CLM API.
* [Learn about the rules and resource limits](/docs/clm-api/clm101/rules-and-limits) enforced in the CLM API.
* [Learn how to go-live](/docs/clm-api/go-live) with a CLM API integration.
* Create an account and learn about core Docusign functionality with the [Docusign platform](/platform/build-integration).

## Docs

- [Authentication Overview](https://developers.docusign.com/docs/clm-api/clm101/auth.md): This page gives an overview of authentication for CLM v2.0.
- [Salesforce Client Authentication](https://developers.docusign.com/docs/clm-api/clm101/salesforce-clients.md)
- [Object API](https://developers.docusign.com/docs/clm-api/clm101/object-api.md)
- [Task API](https://developers.docusign.com/docs/clm-api/clm101/task-api.md)
- [Content API](https://developers.docusign.com/docs/clm-api/clm101/content-api.md)
- [Response and Error Codes](https://developers.docusign.com/docs/clm-api/clm101/response-error-codes.md)
- [API Rules and Resource Limits](https://developers.docusign.com/docs/clm-api/clm101/rules-and-limits.md)
- [Cross-Origin Resource Sharing (CORS)](https://developers.docusign.com/docs/clm-api/clm101/cors.md)