API

Rate and resource limiting

Mutual TLS Edge Truststore imposes various limits on the number of requests you can make and resources you can deploy.

Rate limiting

All Mutual TLS Edge Truststore API endpoints limit throughput to a certain number of requests in each time period. These limits are set per account regardless of the number of users or API credentials from that account accessing the Mutual TLS Edge Truststore. The API returns a status code of 429 if rate limits are exceeded.

Account rate limits

All Mutual TLS Edge Truststore API endpoints limit throughput to a certain number of requests in each time period. These limits are set per API per account, regardless of the number of users or API credentials from that account accessing the Mutual TLS Edge Truststore. The API returns a status code of 429 if rate limits are exceeded.

When you exceed the rate limit threshold, the API responds with an error, as shown in this example:

{
  "rateLimitReset":"2023-10-27T19:23:55Z",
  "instance":"/mtls-edge-truststore/error-types/rate-limit-exceeded?traceId=-8849688147311234963",
  "rateLimit":2,
  "rateLimitNext":"2023-10-27T19:23:55Z",
  "detail":"Quota has been exhausted. You can submit the request after 280 seconds",
  "type":"/mtls-edge-truststore/error-types/rate-limit-exceeded",
  "title":"Rate Limit Exceeded",
  "rateLimitRemaining":0,
  "status":429
}

The API includes these response headers to indicate rate limits:

🚧

Rate limit change

Rate limits may change without prior notice to protect and ensure platform stability.

LimitDescription
X-RateLimit-LimitIndicates how many total requests you are allowed to make in the current time window. You can’t make more requests than this value.
X-RateLimit-RemainingIndicates how many remaining requests you can make in the current time window.
X-RateLimit-ResetIndicates the time of resetting the number of your remaining requests to the full limit indicated by X-RateLimit-Limit.
X-RateLimit-NextIndicates the time when you can make the next request after exhausting the requests in the current time period. This header only appears in 429 error responses when you hit the rate limit threshold.

When you exceed the rate limit threshold, the API responds with an error like this:

{
    "rateLimitReset": "2023-10-27T19:23:55Z",
    "instance": "/mtls-edge-truststore/error-types/rate-limit-exceeded?traceId=-8849688147311234963",
    "rateLimit": 2,
    "rateLimitNext": "2023-10-27T19:23:55Z",
    "detail": "Quota has been exhausted. You can submit the request after 280 seconds",
    "type": "/mtls-edge-truststore/error-types/rate-limit-exceeded",
    "title": "Rate Limit Exceeded",
    "rateLimitRemaining": 0,
    "status": 429
}

Global rate limits

The Mutual TLS Edge Truststore API has system-wide limits in place to ensure overall stability, which are separate from your account's limits. If these global limits are reached, you may receive a 503 error even if you haven't hit your account's quota. This is typically a temporary state. If you run into this issue repeatedly, contact your Akamai account representative.

{
   "retryAfter":10,
   "instance":"/mtls-edge-truststore/error-types/global-rate-limit-exceeded?traceId=-8849688147311234963",
   "detail":"Server temporarily unavailable. Try again in 10 seconds.",
   "type":"/mtls-edge-truststore/error-types/global-rate-limit-exceeded",
   "title":"Global Limit Exceeded",
   "status":503
}

Resource limiting

Mutual TLS Edge Truststore API imposes limits on CA sets you can activate. The API does not expose the number of remaining CA sets.

You can create at a maximum:
· 200 CA sets per account
· 100 versions per CA set
· 300 certificates per CA set version.

The API returns a status code of 422 if these resource limits are exceeded.