Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hello folks,For several years we've documented and expanded the list of supported base URIs as we've expanded global access to Meraki. Undocumented base URIs--that is, any base URIs not on this list--are not supported and also are not subject to any ...
Hello folks,In our OpenAPI spec we name the operation paths to use when making API requests. These are the only paths that should be used for dashboard API requests. Making API requests to undocumented paths can mean your application suddenly stops w...
Good morning team,With 1.53.0 we're releasing these new operations which can streamline your telemetry gathering. If you are using getDeviceSwitchPortsStatuses at any scale, iterating over the devices in your organization, then these new operations, ...
Hello folks,In our dashboard API authorization docs we name the base URIs (e.g. https://api.meraki.com/api/v1 for US Commercial) to use when making API requests. These are the only base URIs that should be used for dashboard API requests. Making API ...
Please find the following information about caveats involved when enabling Early API Access on production organizations.https://community.meraki.com/t5/Developers-APIs/UPDATED-Beta-testing-with-the-Meraki-Developer-Early-Access/m-p/145344#M5808
Hi @Micah_Billman, seconding @alessandrodematos's advice above. Here are some things to keep in mind when working with device availability and the API:Update Frequency: The API (even old versions) only updates device status about once every five minu...
Hi @SwapnilZ , I'd recommend checking out the following operations:https://developer.cisco.com/meraki/api-v1/get-organization-devices-availabilities-change-history/https://developer.cisco.com/meraki/api-v1/get-organization-devices-availabilities/http...
