Overview
Rate limiting is a strategy to manage network traffic. Systems such as ours do this to ensure that the service isn’t overwhelmed by third parties that we have little control over the implementation.
It also helps mitigate from more malicious activity from bots and attackers.
Related documents:
- Sending Leads To The Convertr Platform (Publisher API)
- POST Leads To The Convertr Platform (Campaign Webhook)
Rate Limits
From the 18th December 2023, Convertr will be enforcing the following rate limits to ensure the best service for our customers:
| Endpoint type | Approximate limit | If exceeded |
|---|---|---|
| Login & authentication | ~20 requests per minute | Temporary challenge or HTTP 429 |
| Publisher / lead-result (bulk integrations) | ~400 requests per minute (sustained average) | HTTP 429 |
General API (/api/*) |
Bursts up to ~10 requests per second | HTTP 429 |
| All other traffic (UI, tracking, assets) | Short bursts allowed; ~25 requests per second sustained | Temporary challenge, then HTTP 429 |
In order to align to these rate limits we recommend:
- Designing your integrations to reuse access tokens for their lifetime (currently 60 minutes)
- Staggering requests over period of time and keeping the number of concurrent requests under 10
- Regularly reviewing your implementation to ensure it’s suitability
Any requests which exceed the limit will be met with a 429 Too Many Requests response until the end of the 5 minute rolling window.
This change applies to all requests across the Convertr platform not to a single client endpoint.