Rate Limits
The impact.com application programming interface (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.
Response headers
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:
X-RateLimit-Limit-hour
Maximum requests allowed in the current hour.
X-RateLimit-Remaining-hour
Requests remaining in the current hour.
RateLimit-Limit
Maximum requests allowed in the current window.
RateLimit-Remaining
Requests remaining in the current window.
RateLimit-Reset
Seconds until the current window resets.
Retry-After
Only on 429 responses. Seconds to wait before retrying.
Hourly rate limits
Endpoints are grouped, and all endpoints in a group share that group's limit.
Batch logging
40,000 requests per hour
Batch and FTP resources under /Agencies/{AgencySid}/Advertisers/{AdvertiserId}/
Catalogs
3,600 requests per hour
/Agencies/{AgencySid}/Advertisers/{AdvertiserId}/Catalogs and /Agencies/{AgencySid}/Advertisers/{AdvertiserId}/FinancialCatalogs
Reports
1,000 requests per hour
/Agencies/{AgencySid}/Reports
General
1,000 requests per hour
/Agencies/{AgencySid}, and resources directly under a brand (/Agencies/{AgencySid}/Advertisers/{AdvertiserId}/{Resource}), including ReportExport
Report exports don't have a daily limit for agencies.
Endpoints without rate limits
The following endpoints under /Agencies/{AgencySid}/Advertisers/{AdvertiserId}/ aren't rate limited:
POST,PUT, andDELETEonActionsMobileEvents,MobileDetails,Conversions, andAppEvents
Example rate limit responses
These examples show the headers in a successful response and in a rate-limited response.
Request within the limit
Limit exceeded
Last updated

