Quotas
To ensure maximum availability, Yandex Metrica caps the rate of API requests that can be sent by users. If quotas are exceeded, all further actions by the user are temporarily blocked. In this case, the API returns a response with the HTTP status 420 Too Many Requests. The message body contains information about the type of quota exceeded.
|
Restriction |
Quota |
Lifting the quota block |
|
Number of requests from a single IP address |
30 requests to the API per second |
When the number of requests to the API made in the last second drops below 30. |
|
10 requests to the Logs API per second |
When the number of requests to the Logs API made in the last second drops below 10. |
|
|
Number of parallel requests per user ( |
3 requests |
When the number of parallel requests to the API drops below 3. |
|
Number of requests per user ( |
5000 requests per day |
At 00:00 Greenwich Mean Time (GMT) |
|
Number of requests to the Reports API (url |
200 requests per 5 minutes |
5 minutes after exceeding the quota |
|
400 report requests via the interface per 5 minutes |
||
|
Number of requests per tag |
||
|
Number of added representatives per tag |
3 per hour |
At the start of each hour (00 minutes) |
|
Number of requests for access to a single tag |
Rate limits are calculated separately for each group of API methods:
client_read: Reading parameters for a tag or a Yandex Metrica user account. All the methods in the Management API belong to this group.client_write: Saving parameters for a tag or a Yandex Metrica user account.report_read: Getting data from Yandex Metrica reports. This group includes methods in the Reports API, the Report Builder, and the API that is compatible with the Google Analytics Core Reporting API.