The impact.com API limits how many calls a client can make in a given hour to help protect our system against traffic spikes that could disable it. If the number of requests you are trying to make exceeds your limit, your requests will be throttled and we will respond with a 429 - Too Many Requests response along with the following headers:
| Attribute | Description |
|---|---|
| X-RateLimit-Limit | Maximum number of requests allowed for the resource within the given time period. |
| X-RateLimit-Remaining | Number of requests left as of the current request within the given time period. |
| X-RateLimit-Reset | Number of seconds until the limit is reset. This is in-line with IETF standards. |
Each app may have different default rate limits. By default, the impact.com system limits users to 1,000 requests per hour. Certain resources like Conversions are not limited. Also, the Catalogs endpoint has a limit of 3,600 requests per hour. This is subject to change at any given time based on the needs of the system. It is best practice for applications to monitor their current rate limit status and dynamically throttle requests if necessary.
Example Rate Limit Headers
HTTP/1.1 200 OK
Content-Type: application/json
X-RateLimit-Limit: 100
X-RateLimit-Remaining: 100
X-RateLimit-Reset: 1487332519
HTTP/1.1 429 Too Many Requests
Content-Type: application/json
X-RateLimit-Limit: 100
X-RateLimit-Remaining: 0
X-RateLimit-Reset: 1487332519
