Can we control  uplink Band width Usage on APs using API. ... View more

Is their is an API that can be use for the up link Usage Monitoring of an AP? ... View more

Can we ping Meraki APs via an API? ... View more

from meraki_sdk.meraki_sdk_client import MerakiSdkClient from meraki_sdk.models.update_network_device_model import UpdateNetworkDeviceModel from meraki_sdk.exceptions.api_exception import APIException x_cisco_meraki_api_key = 'X-Cisco-Meraki-API-Key' client = MerakiSdkClient(x_cisco_meraki_api_key) devices_controller = client.devices collect = {} network_id = 'networkId4' collect[ 'network_id' ] = network_id serial = 'serial0' collect[ 'serial' ] = serial update_network_device = UpdateNetworkDeviceModel() update_network_device.name = 'My AP' update_network_device.tags = ' recently-added ' update_network_device.lat = 37.4180951010362 update_network_device.lng = -122.098531723022 collect[ 'update_network_device' ] = update_network_device try : result = devices_controller.update_network_device(collect) except APIException as e: print(e) ... View more

Rate Limit The Dashboard API is limited to 5 requests per second, per organization. A burst of 5 additional calls are allowed in the first second, so a maximum of 15 calls in the first 2 seconds. The rate limiting technique is based off of the token bucket model. An error with a 429 status code will be returned when the rate limit has been exceeded. RATE LIMIT ERRORS ​If the defined rate limit is exceeded, Dashboard API will reply with the 429 (rate limit exceeded) error code. This response will also return a Retry-After header indicating how long the client should wait before making a follow-up request. The Retry-After key contains the number of seconds the client should delay. A simple example which minimizes rate limit errors:​   response = requests.request("GET", url, headers=headers) ​ if response.status_code == 200: # Success logic elif response.status_code == 429: time.sleep(int(response.headers["Retry-After"])) else: # Handle other response codes   Expect to backoff for 1 - 2 seconds if the limit has been exceeded. You may have to wait potentially longer if a large number of requests were made within this timeframe.   Source: https://documenter.getpostman.com/view/7928889/SVmsVg6K?version=latest   Another thing you should consider is using   action batches. That'll help to optimize your workflow, thus lowering the amount of calls needed. Check this blog post for all info on that: https://meraki.cisco.com/blog/2019/06/action-batches-a-recipe-for-success/ View solution in original post ... View more

for get_organization_uplinks_loss_and_latency  what values can be used for t0,t1 or Timestamp to get the past 12 hour data      t0 The beginning of the timespan for the data. The maximum lookback period is 365 days from today.   1 t1 The end of the timespan for the data. t1 can be a maximum of 5 minutes after t0. The latest possible time that t1 can be is 2 minutes into the past.   2 timespan The timespan for which the information will be fetched. If specifying timespan, do not specify parameters t0 and t1. The value must be in seconds and be less than or equal to 5 minutes. The default is 5 minutes. ... View more