CleverTap · Rate Limits

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, conforming to the API Commons Rate Limits specification.

It captures 23 rate-limit definitions, measuring concurrent_requests.

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.

23 Limits Throttle: 429
Rate LimitingQuotasThrottlingConcurrency

Limits

Upload User Profiles account
concurrent_requests
15
Upload Events account
concurrent_requests
15
Upload Device Tokens account
concurrent_requests
15
Catalog API account
concurrent_requests
3
Create Campaign account
concurrent_requests
3
Create Segment account
concurrent_requests
3
Update Segment account
concurrent_requests
3
Custom List API account
concurrent_requests
3
Delete User Profile account
concurrent_requests
3
Demerge User Profile account
concurrent_requests
3
External Trigger API account
concurrent_requests
3
Get Campaign Report account
concurrent_requests
3
Get Campaigns account
concurrent_requests
3
Get Event Count account
concurrent_requests
3
Get Events account
concurrent_requests
3
Get Message Reports account
concurrent_requests
3
Get Profile Count account
concurrent_requests
3
Get User Profiles account
concurrent_requests
3
Raise a Bulletin account
concurrent_requests
3
Real-Time Counts account
concurrent_requests
3
Stop Scheduled Campaign account
concurrent_requests
3
Top Property Counts account
concurrent_requests
3
Trends account
concurrent_requests
3

Policies

Exhaustion behavior
Requests beyond the concurrency ceiling are rejected with HTTP 429 and the message "Too many concurrent requests". Because there is no window, the correct client behavior is to cap in-flight parallelism at the documented number rather than to pace by time.
No documented backoff contract
CleverTap publishes no Retry-After value and no reset timestamp. Clients must implement their own backoff.