> 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

# Rate Limits

## Rate Limits

> **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 has rate limits that are currently set high enough that they should not be reached under normal usage of the API. In the case that a rate limit is exceeded, a 429 response code will be sent back along with some additional information. There are two different ways to exceed an API rate limiter: too many requests for a Docusign CLM account within a given time period of time and too many concurrent requests for a single user. Sample JSON responses for each type of limit are shown to the right:

* **Exceed the concurrent number of requests for a given user**
* **Exceed the number of requests for an account in a given time period**

When the number of requests for an account is exceeded the customer header **X-RateLimit-Reset** will be returned that will hold the date/time of when requests for the account can resume.