Did you get it figured out?  It's just a POST in whatever language you are using. (I use perl/curl). You POST the data as shown, "0" being the first SSID in your list in the GUI as shown above, "1" being the second etc.  POST to the client provisioning api.  I use version0 for this, I'm not sure it works in the v1 api.   Perl might look something like this: $curlstring = 'curl -H X-Cisco-Meraki-API-Key:'.$KEY.' -H Content-Type:application/json -X POST --data-binary "{\\"mac\\":\\"'.$macaddress.'\\",\\"name\\":\\"'.$computername.'\\",\\"devicePolicy\\":\\"Per connection\\",\\"policiesBySsid\\":{\\"0\\":{\\"devicePolicy\\":\\"Blocked\\"},\\"1\\":{\\"devicePolicy\\":\\"Whitelisted\\"}}}" https://api.meraki.com/api/v0/networks/N_12345etc890/clients/provision'; $result = `$curlstring`; But what ever way you post it, just be sure to post it to the wireless network your client is in just as if you are "provisioning" it.   Don't know if that helps, or makes it worse 😋 Cheers ... View more

I don't know if this got solved for any of you folks, but I found the proper format to send a client per SSID policy. Maybe this will help someone that finds this... took me awhile to get it.    Make sure to have the correct number of SSIDs definded.   { "policiesBySsid": { "0": { "devicePolicy": "Blocked" }, "1": { "devicePolicy": "Whitelisted" }, "2": { "devicePolicy": "Blocked" } }, "mac": "00:aa:bb:11:22:aa", "name": "Test", "devicePolicy": "Per connection" }   ... View more

Thanks for that! I'm using Perl with json module and cURL to get the data. So up until now I haven't been looking at the headers at all.   CURL -i  will show the headers and it does indeed have the link with the last tag. So I'll add that to the bag of tricks for any other pages that have the 1000 limit.  I've only come across it on the org/devices so far and I did notice that the last serial in the returned json array was the "marker" and if I asked for after that I got the next 1000.   Looking at the headers is something I didn't think of.   Cheers! ... View more

Hi, and thanks.  Yes, I've got several scripts where I pull all the networks, or the inventory depending on what I'm doing with the script.  I was writing a script to show all the notes and reset them if I choose.  Pulling from the /devices endpoint I only had to do 1 get (or so I thought).  I'm using perl::json so it's super easy to just check to see if there are less than 1000 elements in the array and if so, do another get with the last serial number pulled.   It was just a surprise to see that by default, the get /devices didn't pull everything, and it makes me wonder if any other endpoints are like that. Just something to be watchful for.   Cheers!     ... View more

I'm actually looking for info about the "perPage" issue with networks/{networkId}/devices It will only return 1000 devices. There is supposed to be  a way to ask for more pages, but with an API we shouldn't have to.   I'm also looking to mass edit notes and the /devices endpoint won't list them all (I have over 2000 devices).   --edit--   So there is a "startingAfter" parameter that will accept a serial number as an identifier. You just have to give it the last serial number in the previous GET and it will carry on from there... networks/{networkId}/devices?startingAfter=QABC-1234-5678   ... View more