Quotas

To ensure maximum availability of the service, Yandex.Audience limits the number of API requests from users.

Two types of limitations are imposed simultaneously:

  • By IP – Limits the rate of requests from a single IP address to 30 requests per second.
  • By user_login – Limits the number of requests from a single user to 5000 requests per day.

The rate of requests is calculated separately for each of the following groups of API methods:

  • client_read – Reading parameters for a segment or user account in Yandex.Audience.
  • client_write – Saving parameters for a segment or user account in Yandex.Audience.
  1. Exceeding quotas
  2. Restrictions on creating and changing segments

Exceeding quotas

If the quotas are exceeded, the user is temporarily blocked from further actions. In this case, the API returns a response with the HTTP status 429 Too Many Requests. The response body contains information about the type of quota exceeded.

If the quota by IP address was exceeded, the address is unblocked when the number of API requests during the last second drops below 30.

If the quota by user_login was exceeded, the user is unblocked automatically at midnight Moscow time (UTC +3).

Restrictions on creating and changing segments

When sending a request to create or change segments of any type, the following restrictions apply:

  • Maximum 10 requests per minute.
  • Maximum 100 requests per hour.
  • Maximum 500 requests per day.

When sending a request to create or change geosegments, the following additional restrictions apply: if your login has 1000 or more segments based on geolocation data and less than 5% of them are used for targeting in Yandex.Direct or Yandex.Display, sending a request to create geosegments isn't possible.

Note.

The quotas include requests that are made by mistake.