Ssl Tls Rate Limits
Multi-vendor category covering ACME and CA-issuance APIs. Let's Encrypt publishes concrete per-account, per-IP, and per-domain limits on the ACME v2 endpoint; DigiCert and Sectigo gate API throughput per partner contract and do not publish numeric per-second limits. Numbers below are sourced from Let's Encrypt's public rate-limit documentation.
Ssl Tls Rate Limits is the machine-readable rate-limit profile for SSL/TLS on the APIs.io network, in the API Commons Rate Limits shape.
It captures 7 rate-limit definitions, measuring certificates, accounts, orders, failures, and varies.
Limit state is signalled in the retryAfter response header, and an exhausted limit returns HTTP 429.
This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled and rateLimited.
Tagged areas include SSL/TLS, TLS, Certificates, PKI, and Certificate Authority.
retryAfter
generated, dated 2026-05-05.
Limits
Policies
Sources
- https://letsencrypt.org/docs/rate-limits/
- https://dev.digicert.com/services-api/
- https://sectigo.com/resource-library/cert-manager-api-documentation
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.