Sneak peak of the API firmware endpoints in beta.   Stay tuned...         ... View more

Unfortunately no, they don't seem to expose that functionality via the API. ... View more

@BrianP is correct. There's always options. I fell into Python personally, so that's the one I can talk most about.   There's an active node.js SDK as well, and I know there are people who use node.js in general heavily for Meraki kit. ... View more

@BrianP wrote: Fair enough. For people who have issues hitting the Rate limit ( due to other active monitoring API calls ), it would be significantly faster to do the network list call and the full org device list call, and correlate the device to the correct network in the code, instead of the individual calls per network. Either way, you solved Raphael's issue! Definitely agree. 🙂 I can do things sloppily sometimes because Auvik and I are the only things making calls, and Auvik rate limits itself.   There are advantages and disadvantages to being the only automator on your team. ... View more

Are you referring to Device Status?  If so @CBurkhead is correct and that call should be sufficient.  If you are looking for availability statistics like if a device is up for 99% of a time period, then they don't have a specific call for that.   You can use the GET /networks/{networkId}/devices/{serial}/lossAndLatencyHistory endpoint to get the packet loss info for a time period.  The inverse of that is close to availability (depending on the availability calc you are going for ). ... View more