Concurrent Requests

Concurrent requests are the maximum number of parallel API requests you can send to CleverTap. Think of this as the system's maximum capacity to handle multiple requests from users simultaneously without causing delays or failures.

When interacting with CleverTap APIs, you might need to perform several operations simultaneously, such as uploading device tokens, retrieving campaign data, or managing user profiles. Each operation is an API request. CleverTap limits concurrent API requests per user account to ensure smooth and efficient processing and maintain service performance and stability.

Here is a practical example to help you understand concurrent requests:

Uploading Device Tokens:Suppose you have a batch of device tokens to upload. The concurrent request limit for this operation is 15, meaning you can send up to 15 upload requests at the same time. If you exceed this limit, the system rejects the extra requests, and you receive an HTTP 429 error with the message Too many concurrent requests.

Importance of Concurrent Request Limits

• Performance: Limits ensure the system handles requests efficiently without overloading, providing consistent and reliable performance.
• Fair Usage: Prevents one account from using all the available resources.
• Stability: Maintains overall service stability and availability by managing the load.

Understanding concurrent request limits helps you manage your API usage, avoid exceeding limits, and ensure smooth application performance.

Concurrent Request Limits for APIs

The following table lists the maximum number of concurrent requests allowed per user account for an API:

📘

Note

CleverTap does not enforce rate limits based on specific time frames (minute, hour, or day), making our APIs more accessible.