The best solution is: 1) Fetch all clients via GET /networks/{networkId}/clients| 2) Put the fetched clients into a hashtable (Map) with client.id as a key and client as a value. 3) Fetch all clients with group policies via GET /networks/{networkId}/policies/byClient  4) Match clients with policies to clients by client.id, using the Map from step 2. In the end, you will have all clients with their corresponding group policies collected in 2 requests to Meraki API. Both getClients and getNetworkPoliciesByClient requests support pagination with page size up to 1000. ... View more

Just want to add my vote for this too.   I've submitted this a number of times and raised it in a community post.   We also use an NMS and still to this day can't get proper traffic stats from our MX's   Given the lack of response I can only imagine they've done it intentionally to force you to use their web dashboard. Doesn't make sense to me. 🤷🏼‍♂️   ... View more

One of the major p[rojects i have recently done is the following :   We have several vessels which are connected with V-Sat... These have a low bandwidth and high latency. Here we have some SD WAN and Traffic shaping rules, however if a vessel is near the shore, they automatically select a different carrier with a higher speed and a lower latency. That means that the Traffic shaping can be different , and the crew can be granted more bandwidth.   I have created a Python script which checks changes in latency, and changes the WAN1/WAN2 speed of the meraki and adjust the speed of the crew wifi accordingly.....    When the vessel returns to the V-Sat again, the script changes it back to the original set WAN1/WAN2 speeds and SD Traffic shaping...   This is the power of Meraki API   ... View more