I think the statuses just match the ones listed in the main documentation...   https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Status_Icon_Meanings   ...from that page:   Every device can display in one of four colors, indicating the status of that device:   Green:   The Cisco Meraki device is currently online and has no alerts Yellow:  The Cisco Meraki device is currently online but has one or more active alerts Red:      The Cisco Meraki device is currently offline and is inaccessible by the Cisco Meraki Dashboard Grey:     The Cisco Meraki device is currently offline and has been offline for at least a week (dormant).   These indicators can be a quick and easy way to narrow down what sort of trouble a device is experiencing. A device indicating it is offline likely cannot reach it's gateway or Dashboard. A device indicating a yellow alerting status will often have additional details on the device details page. Examples include IP address conflicts or disconnection from RADIUS. ... View more

A key will work until the Administrator who created it revokes it. If the Admin in question is removed as an Admin from any Organization (Org), that key will no longer work within that Org.   If he/she remains an Admin in other Orgs, it would continue to work in those.. https://documentation.meraki.com/General_Administration/Other_Topics/Cisco_Meraki_Dashboard_API#Enable_API_Access ... View more

In this case, I would not worry about the response size. I have a script that uses this and other calls, in total it takes just a couple of seconds on an organization with >400 networks and thousands of devices.   It could be that adding extra filters might actually increase the load on the API service - extra processing is needed to check each item against the filter(s), rather than just sending 'everything'.     ... View more