You might find this useful.  You supply the serial number of a device, and it returns all clients of that device. https://developer.cisco.com/meraki/api-latest/#!list-the-clients-of-a-device-up-to-a-maximum-of-a-month-ago  ... View more

I think this is the key endpoint that you'll need:   https://developer.cisco.com/meraki/api-v1/#!update-network-appliance-vlan ... View more

Check out this endpoint https://developer.cisco.com/meraki/api-v1/#!update-device   Keep in mind that the notes field has a length limit. ... View more

I really need to find the answer to my original question.  Different API calls will not accomplish what I am wanting.  I need the total GB or MB from a week's time flowing only from one SSID.  I don't need to drill down to a client to get client data.     I don't need the top devices.  I need all devices. ... View more

Exactly what I was looking for!  Thanks Alemabrahao. ... View more

You don't say what version you came from.   V17.x uses the new Snort V3.x IPS engine and the Cisco TALOS content filtering engine.  The Snort engine in particular supports more things and uses more CPU power. ... View more

You can filter the events returned by the call, this is the list I use for getting block events...   nbar_block, cf_block, sf_url_block, sf_binary_block   Note that if you use the Python library there can be an issue if there are no events, see this thread for the workaround I use... https://community.meraki.com/t5/Developers-APIs/Events-same-event-different-API-return-also-call-never-returns/m-p/182558   ... View more

Just wondering if you might need an interim step to permit multiple VLANs: PUT /networks/{networkId}/appliance/vlans/settings   ->    { "vlansEnabled": true }   https://developer.cisco.com/meraki/api-v1/#!update-network-appliance-vlans-settings ... View more

There is an event log event type for Primary Uplink Status Change that you could use. I assume that your primary interface is WAN1. An event will be generated upon failure and again for when it is restored. The event type to filter by is failover_event.   https://developer.cisco.com/meraki/api-v1/#!get-network-events   ... View more

Not the answer you are looking for, but some alternatives:   Network-Wide/Traffic Analytics shows the top applications that have been used.  You enable this under Network-Wide/General (in case you have it turned off).   Organization/Summary report also has some info, and you can schedule this one to be enabled to you on a regular basis. ... View more

Ahhh, that second call requires you to specify device or client, you'd need to run it on each AP.   The first call I mentioned is simpler as you run it per-network, I suggest stick to that one. ... View more

Are these wireless only networks or combined networks? The endpoint you mentioned should list wireless only networks. It works in my org. ... View more

Haven't tried this, but looking at the documentation...   You get the node_mac in the initial request sent to your splash server.   When you craft your continue_url, can't you do it based on the node_mac?   You can optionally add a continue_url and a duration query to tailor the login process. To send the client onto their intended site, copy the user_continue_url value into the continue_url parameter.   I.e. instead of using the default user_continue_url value, choose the continue_url you want based on node_mac, for instance you could use the same host/path and just add the node_mac value on the end of the URL as a parameter. ... View more

If you are not using the Python library and if there are a lot of devices you'll need to handle multipage results, are you doing that?   Set the productTypes parameter (it's an array) to just one element "wireless", then you'll only get matching devices returned. Makes it simpler.   ... View more

@tjh188 - this is where we may be able to help!   We author the Meraki.Api nuget package for the purpose of Meraki automation.  See https://www.nuget.org/packages/Meraki.Api/ if you are familiar with .NET development.   If not, but you have a modest budget, we can do the required development for you. ... View more

Be aware the maximum lookback stated in the documentation is "31 days", whether this is simply 86400*31 seconds or some other period isn't stated. But if you miss a run for some reason, or there is a network/API/other glitch (these things happen), you may run out of time to recover before losing data.   I recommend use the Python library with async IO to run on all networks concurrently (underlying is rated limited, but the library handles that for you) as you will be issuing call-per-network, this will run faster than network at a time.   Fwiw for testing I currently run it daily with 600 second resolution and build a long-term time series, same as the approach for a number of other things we measure, the automation handles some re-runs itself, or we can recover manually by setting t0-t1 as appropriate.   ... View more