Rate limiting
3 minute read
Rate limiting protects the stability, performance, and availability of the DigiCert® Trust Lifecycle Manager APIs. It controls the number of requests a client can make within a defined period.
Without rate limiting, a single client generating excessive requests, a misconfigured integration, or repeated retries can consume shared capacity and negatively affect other customers. Rate limiting helps mitigate these risks by enforcing configurable request limits at the platform level.
How rate limiting helps
- Fair resource usage: Prevents a single account or profile from consuming a disproportionate share of available resources.
- Improved platform stability: Rejects requests that exceed configured limits before they reach the application services.
- Predictable performance: Helps manage traffic spikes and maintain consistent service availability under varying request loads.
- Configurable limits: Supports request limits tailored to observed traffic patterns and platform capacity.
This guide explains which Trust Lifecycle Manager requests are limited, how each limit is scoped, what your client receives when it hits a limit, and how to build clients that handle it gracefully.
Before you begin
This guide assumes you understand:
429 Too Many Requests responses. See the DigiCert API error reference for general HTTP error handling.API rate limits and scope
Trust Lifecycle Manager applies a different per-minute rate limit to each API group. Public API requests are counted per customer account, while EST, SCEP, and CMP requests are counted per enrollment profile.
| API group | Requests per minute | Limit applied per | Details |
|---|---|---|---|
| Public APIs | 5,000 | Customer account | All requests that your account sends to these APIs count against that account’s allowance, so a busy integration can affect other users of the same account. |
| SCEP | 1,000 | Enrollment profile | All clients using the same SCEP enrollment profile share that profile’s allowance. |
| EST | 500 | Enrollment profile | All clients using the same EST enrollment profile share that profile’s allowance. |
| CMP | 500 | Enrollment profile | All clients using the same CMP enrollment profile share that profile’s allowance. |
How it works
Each request is checked against the applicable limit: the customer account limit for Public APIs or the enrollment profile limit for EST, SCEP, and CMP. A request within the limit is processed unchanged. A request over the limit is rejected with HTTP 429 Too Many Requests, and it isn’t processed.
Rate limits use a fixed one-minute window. The counter resets to zero at each minute boundary, regardless of incoming traffic.
Every request counts toward the limit, including requests that receive an HTTP
429response. A client that continues sending requests after exceeding the limit receives429responses until the next minute boundary.The API does not return
X-RateLimit-*orRetry-Afterheaders. Clients should implement their own backoff logic before retrying.
See the DigiCert API error reference for general HTTP error handling.
Request a higher limit
If your integration needs more capacity, contact DigiCert Support to request a higher limit for your account or enrollment profile. You can reach DigiCert through Contact DigiCert.
Related topics
- DigiCert API error reference: General HTTP error handling.
- Trust Lifecycle Manager API reference: Operations and documented responses.
- Bulk revoke multiple certificates: A tutorial whose workload can generate many requests.
- Request a TLS certificate: A tutorial for issuing a certificate.