Hey y'all, I've been having some trouble with getting the vlan query to work on the Get Network Clients endpoint (/networks/{networkId}/clients). I'm able to make the calls and retrieve the payloads with any other querys with no issue, but the vlan query just doesn't work at all. I've tried just about everything, but nothing.
My best guess is that it's either expecting a string, while the actual data is an integer, or the opposite is happening. Specifically, the reason that seems plausible to me is that when setting the vlan parameter in the online console, it shows as an integer in the Curl template tab, while the documentation clearly states that it should be a string. I'd think adding quotes to it would fix it, but no dice there.
Furthermore, the v0 api documentation for the same option actually does show the vlan field as an integer in the response payload instead of a string like the v1 endpoint returns:
v1
v0
I'm tempted to think there might just be something wrong in the documentation since I've found some other things that weren't very clear so far that have lead me to distrust the documentation a bit. It took me quite a while to figure out that the 'statuses' and 'recentDeviceConnections' query's don't work without adding brackets ('statuses[]' and 'recentDeviceConnections[]') despite no note of it in the doc and the console in the documentation putting them in in a broken state without them by default (implying that that is the correct way to use them).
Does anyone know whether I'm just missing something or if this actually is just broken?
The documentation states that vlan is a string , but when looking at the Template Python request it is shown as a Integer. Weird...
When testing with a simple GET query : https://n378.meraki.com/api/v1/networks/L_XXXXXXXXXXXXX/clients?vlan=VALUE
I tried vlan=X , vlan="X" vlan=SomeGarbage and none of them returns en error , but none of them returns the expected results.
This is ultra broken and I would suggest you to open a ticket.
For the last part :
It took me quite a while to figure out that the 'statuses' and 'recentDeviceConnections' query's don't work without adding brackets ('statuses[]' and 'recentDeviceConnections[]') despite no note of it in the doc and the console in the documentation putting them in in a broken state without them by default (implying that that is the correct way to use them).
That behavior is expected since the documentation states that these values are arrays.
Thanks for confirming that it's not just me with your test. I've submitted a ticket, so I'll let y'all know when I get an update.
On the second part, the main thing that I was referring to was that the console automatically fills in both of those fields incorrectly, which causes confusion. I think it's fair to assume that the built in testing tool is showing the query correctly. Maybe I'm naive, but to me it led me to believe I was using it correctly until I found forum threads with other's who ran into the same confusion. At the very least, if it's a common enough issue to find multiple threads with people who are similarly confused, it might be worth it for them to make more clear in the documentation.
I have also found that If you delete a parameter , the content of the parameter is transfered to the next parameter ...
Look what happened to ip6 when I deleted an upper parameter :
This is a weird behavior. I'm on Chrome 98 btw
