API Limits

Overview

Rate limits are an essential part of any API. They help maintain the stability, reliability, and overall performance of the system by preventing excessive or abusive usage. By controlling how frequently requests can be made, rate limits ensure that resources are distributed fairly and that all users are able to access the API with a consistent and dependable level of service.

CMap API rate limits

CMap limits API calls across your Tenant as a whole; This means that multiple client applications or integrations share a rate limit when integrating with your CMap instance.

If your integration spans multiple CMap Tenants & serves multiple CMap clients, calls to each of them will be rate limited individually and will not affect the other.

For all CMap integrations, the rate limits applied are:

Concurrent Limit: No more than 10 calls in progress at a time (within 1 second)
Minute Limit: No more than 300 calls within the space of 60 seconds

Note that we cannot reset a limit for you once hit.

Rate Limit Responses

If your request is rate limited, your call will be rejected with an HTTP 429 "Too Many Requests" status code. No matter which limit has been hit, the time (in seconds) of how long you'll have to wait to start making calls again will be returned in a "Retry-After" header.

HTTP/1.1 429 Too Many Requests
Content-Length: 51
Retry-After: 60
<!--Additional Headers omitted for brevity-->

"Request limit of 300 requests per Minute exceeded"

Note that these responses are industry-standard and many API client libraries will handle an HTTP 429 response automatically; waiting for the number of seconds communicated via the "Retry-After" header, and retrying the request for you.

Tenancy