Introduction
This document outlines the restrictions imposed on the rate at which you can make requests to the Meraki Dashboard API. The rate limits mentioned in this document specify the maximum number of API requests you can make within a certain time frame.
Rate Limits
Per source IP address
Each source IP address that initiates API requests is allocated a call budget of 100 requests per second, regardless of the number of API clients operating from that IP address.
Per Organization
- Each Meraki organization has a call budget of 10 requests per second.
- For instance, a total of 10 additional requests are allowed in the first second, so a maximum of 30 requests in the first 2 seconds.
- Rate limiting technique is based on the token bucket model.
- Furthermore, a concurrency limit of 10 concurrent requests per IP is enforced.
| API URL | Number of API Hits per Organization |
|---|---|
| https://api.meraki.com/api/v1/organizations | 1 |
| https://api.meraki.com/api/v1/organizations/549236/networks | 1 per organization |
| https://api.meraki.com/api/v1/networks/L_610800699462127762/wireless/ssids | Total networks |
| https://api.meraki.com/api/v1/networks/L_646829496481108255/devices | Total networks |
| https://api.meraki.com/api/v1/networks/L_566327653141843049/clients | Total networks |
| https://api.meraki.com/api/v1/networks/L_566327653141843049/wireless/connectionStats?timespan=172000 | Total networks |
| https://api.meraki.com/api/v1/networks/L_566327653141843049/wireless/latencyStats?timespan=172000 | Total networks |
| https://api.meraki.com/api/v1/devices/Q2LD-ZWCZ-UA77/wireless/connectionStats?timespan=172000 | Total networks * Total devices |
| https://api.meraki.com/api/v1/devices/Q2LD-ZWCZ-UA77/wireless/latencyStats?timespan=172000 | Total networks * Total devices |
| https://api.meraki.com:443/api/v1/organizations/681155/devices/statuses | 6 per organization |
| https://api.meraki.com/api/v1/devices/Q2HP-7ZQY-VTTC/switch/ports/statuses | Total networks * Total devices |
| https://api.meraki.com/api/v1/devices/Q2QN-Q6EY-NP7J/appliance/performance | Total networks * Total devices |
Note
- When onboarding many devices in a Meraki integration, you may encounter rate limit restrictions imposed by Meraki. To prioritize monitoring, we recommend assigning only the device status monitor. This metric is efficiently collected through a single API call for an entire organization and has been moved to the integration level for better performance. Device status metrics for all devices are collected every 5 minutes and displayed in the graph based on the template assignment.
- OpsRamp implemented a retry mechanism to handle 429 rate limit responses from the Meraki API. When a rate limit is hit, we wait for the duration specified in the Retry-After header, which can vary from 1 minute to 10 minutes based on the request load to that organization. Consequently, there may be gaps in the metrics data for certain timeframes. For more details about the Retry-After header, refer to
- If customers use the same Meraki credentials across multiple integrations or access the Meraki API outside of our platform, they may encounter 429 rate limit errors if the API usage exceeds the limits specified in the documentation. To avoid these issues, please use Meraki reasonably to stay within rate limits. OpsRamp recommends using only one Meraki integration and advises against accessing these APIs outside of our platform.
- Due to the restriction of 10 API calls per second per organization, the API calls are limited internally by OpsRamp to stay within these rate limits. While these optimizations are implemented, there may be occasional missing data samples within the selected timestamp due to delayed processing necessary to comply with the rate limits.