Rate Limits
Request limits enforced per token, user, and marketer.
The following rate limits will be enforced to different levels of the API starting November 1, 2016:
- Authentication requests to obtain token (
/login) limited to 2 requests per hour per user. - Usage of a single token limited to 30 requests per second for the entire API.
- Each marketer is limited to 30 requests per minute for the entire performance reporting API (see Reports rate limits).
- Each marketer is limited to 50 requests per minute for the entire realtime performance reporting API (see Realtime reports rate limits).
In any case of rate limit violation the response status will be 429 (Too Many Requests).
Responses with 429
status also contain HTTP Header rate-limit-msec-left, whose value marks the remaining number of
milliseconds left in which the rate limit will be in effect. For exmple, if the value of rate-limit-msec-left
is 35024, each request within the next 35.024 seconds will violate the rate limit and return with response
status 429. Only requests issued after more than 35.024 seconds will be served.
Given the limitation on /login requests, the recommended way to manage tokens is to store an active
token to be used in all requests, and periodically update it. Since each token is valid for 30 days,
the update period should be 30 days or less.