Most likely, device availabilities in the relevant successor, but check our deprecation page: https://developer.cisco.com/meraki/api-v1/deprecated-operations/#deprecated-operations. We will have the deprecation banner refer to this page for easier discoverability. I hope this helps.
... View more
Thanks for the feedback, @RaphaelL. This operations is still in beta and not widely used yet, which means we can still influence and enhance it to address your comments. I'll make sure the relevant team takes your feedback into consideration.
... View more
The API call you are trying to make would return aggregated information, I don’t see much difference. Can you perhaps explain the use-case, the data you’re trying to obtain, and how it would be used?
... View more
I see. Assuming you’re using the same timespan, maybe one of these clients had no traffic during that time. If you’re listing all clients, would it make more sense to use getNetworkTraffic?
... View more
Question. When using updateNetworkApplianceFirewallL3FirewallRules, the input is an array of rules. Are you seeing different behavior between Terraform, Postman, Python, etc’? If so, can you share the Terraform plan you’re using?
... View more
Hey Raphael, recentDeviceConnections can help you filter wired from wireless. However, won't differentiate between a security appliance and a switch. Would that help?
... View more
Currently, for a use-case of creating new organizations - API keys would make more sense. Configuration changes, compliance, monitoring - these can be achieved with OAuth. As long as the OAuth refresh token is used at least once every 90 days - the integration will last indefinitely (unless an admin revokes it). https://developer.cisco.com/meraki/api-v1/oauth-overview/
... View more
Creation of networks - yes. Creation of new organizations - no. OAuth follows the principles of zero trust, and if it could create a new organization where it will have full admin rights - it would be considered privilege escalation. What are you trying to achieve?
... View more
Yes. https://developer.cisco.com/meraki/api-v1/deprecated-operations/ We will get this page to be linked to the deprecation banner, so people won’t need to find it themselves.
... View more
In Postman, I made an API call with perPage=3 to ensure I have pagination. In the response HEADERS, you will find the "links" value. The "rel=next" is the attribute that will get you the next "page". <https://api.meraki.com/api/v1/organizations/537758/networks?perPage=3&startingAfter=L_64682949648109888>; rel=next You'll notice the URL is the same, except for the startingAfter value.
... View more
Hi Jamie, There is an internal feature request for making roaming analytics data available via our public API. If you can ask your Cisco account team to add their vote and your details to the request - it would help prioritizing it sooner rather than later.
... View more
The roaming analysis page in Dashboard would show you that information. Regardless to the results, I’d recommend disabling 2.4GHz. It should be enabled on a dedicated SSID only so 5GHz clients won’t even try to connect to it. Once upon a time I wrote this script to prove a point. It should still work.
... View more
This looks like an Ansible playbook for Zabbix. We support the Meraki Ansible collection. I assume the Zabbix community supports the Zabbix Ansible collection. That said, you can use the API analytics page and download the API call log (preferably shortly after an attempt to run this playbook). If the 400 error is coming from Meraki (and not Zabbix) - you'll be able to see the API call being made and probably find the reason it gets a 400 response back. If you don't see the API call in the log, the 400 error might be coming from somewhere else, before an API call is made to Meraki.
... View more
