Clevertap Rate Limits
CleverTap's published API limits, read from its own API Request Limit page on 2026-08-13. This file REPLACES a 2026-05-04 bulk-sweep scaffold that invented per-minute and per-month tiered quotas and X-RateLimit-* headers CleverTap does not publish. The real model is different in kind: CleverTap throttles on CONCURRENCY (parallel in-flight requests per account), not on a time window, and says so explicitly — "CleverTap does not enforce rate limits based on specific time frames (minute, hour, or day)". Limits are per user account and per API, and do not vary by pricing tier.
Clevertap Rate Limits is the machine-readable rate-limit profile for CleverTap on the APIs.io network, in the API Commons Rate Limits shape.
It captures 23 rate-limit definitions, measuring concurrent_requests.
Limit state is signalled in the limit, remaining, reset, and retryAfter response headers, and an exhausted limit returns HTTP 429.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled, throttled_message, quotaExceeded, and serviceUnavailable.
Tagged areas include Rate Limiting, Quotas, Throttling, and Concurrency.
limitremainingresetretryAfter
Limits
Policies
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.