For MX integrated cellular, it is available with... https://developer.cisco.com/meraki/api-v1/get-organization-appliance-uplinks-usage-by-network/ ...you get data for each individual uplink on each devices, typically: wan1, wan2, cellular.   For MG, I don't think there is anything yet.   If you are using the MG as an uplink for an MX, the above call gets you the traffic indirectly, though there'll be some underreporting as MG management traffic will not be in the MX numbers.   ... View more

This will get you the primary device inventory... https://developer.cisco.com/meraki/api-v1/get-organization-inventory-devices/   Where supported, you can get PSUs with... https://developer.cisco.com/meraki/api-v1/get-organization-devices-power-modules-statuses-by-device/   For SFPs it gets fiddlier, try these for switches... https://developer.cisco.com/meraki/api-v1/get-device-switch-ports/   https://developer.cisco.com/meraki/api-v1/get-organization-switch-ports-transceivers-readings-history-by-switch/   ...I don't recall anything for MX SFPs. ... View more

Yes, we had similar experience starting back in 2020, and a long period working with Meraki support getting resolution.   All endpoints returning 'measured' values need reason checking, it's not unique to Meraki API either.     ... View more

This is where you are probably better off using Python/whatever to create a script to do it. ..   get list of networks in org for each network     get mx data   You'll probably get other requests over time that would require this sort of approach to perform efficiently, may as well start now 😀 ... View more

Ok, currently the scope of that page is the list of Client VPN users vs. 'known' users that may have got into the list a variety of ways. I think It's really there to allow granting/removing Client VPN access, hence the lack of any rich API around it.   If you do not have any guest users (i.e. all will have an admin account), you can use https://developer.cisco.com/meraki/api-v1/get-organization-admins/ which gives you all admin users.   If there are guests, I'm not sure, if doing the https://developer.cisco.com/meraki/api-v1/get-network-meraki-auth-users/ call, which you (edit) might need to on all networks to build up the full list, isn't working then I don't think there's a way in the API.   In that case one option is to 'cheat' by making a screenscraper,  or to poke around in the page code and find out the URL used by the "Download as CSV" button, then use that to grab the list as a CSV you can process. ... View more

Ah, now I see.   You are trying to list the page titled "User management portal", is that correct? ... View more

I'm unclear exactly what are you trying to do.   You wrote "...given a number of users that is much lower than the amount that is shown in the UI dashboard for Meraki."   Which Dashboard page are you referring to? Is it Network->Clients?   As @John_on_API says, an 'authorized user' is related to a client device granted access via Meraki Authentication for a network.   An 'unauthorized user' is every client device that hasn't gained access that way, there is no 'user' identity there, it's just a client device.   ... View more

The getDeviceSwitchPortsStatuses call provides power usage (over timespan, default one day) for each port that has PoE enabled, it's the powerUsageInWh value.   This is device level power for an attached device such as an AP.   ... View more

Sounds like you may be using the system's Python, to avoid causing the system problems it discourages making changes.   I suggest use pyenv to create a separate Python environment under your control, and use that for your Meraki/other development. See... https://realpython.com/intro-to-pyenv/ ...it has instructions for Ubuntu.   This is what I always do, I never use the system Python. ... View more

In this context, ** 'unpacks' the dictionary into keyword arguments to the function. ... View more

Try adding ** like this... response = dashboard.switch.updateDeviceSwitchPort( serial, port_id, **response_update, ) ... View more

IWhat you are doing here... response = dashboard.switch.updateDeviceSwitchPort( serial, port_id, name = port_name, enabled = enable, type = port_type, vlan = d_vlan, voiceVlan = v_vlan, allowedVlans = v_allowed, rstpEnables = rstp_enabled, stpGuard = stp_guard, accessPolicyType = access_policy, macAllowedList = mac_allowed, stickyMacAllowedList = sticky_mac_allowed, stickyMacAllowListLimit = mac_allowed_limit, poeEnabled = poe_enabled, ) ...is pass the function arguments irrespective of whether they have a value, which causes the problem.   Instead, you need to build the argument list on the fly, only including things that have  a value.   You have the two mandatory positional arguments, serial and portId, the rest are optional keyword arguments in the form kwarg=value,   I'd think if you build the keyword arguments in a dictionary, you could then pass it to the call.   Something like... #create an empty disctionary the_args = {} #for each keyword arg, if it isn't empty/None add the keyword and value # note for numeric values this test would call 0 false, so you need to # make sure the way you test is appropriate for each keyword value type! if v_allowed: #add the keyword and value to the dictionary the_args["allowedVlans"] = v_allowed #repeat for every keyword, then make the call response = dashboard.switch.updateDeviceSwitchPort( serial, port_id, the_args )   ... View more

What you see in Dashboard is based upon logic/parameters that are not public and also not necessarily derived from the published API calls.   So they may show differing values, that doesn't mean either is 'wrong', simply that the values were arrived at differently.   For instance, this API call only reflects performance for the specified IP, I'd assume Dashboard is reporting loss across all traffic.   This isn't unique to Meraki, I see the same with other platforms with the UI and API not matching.   It's just something you have to live with, trends and qualitative indicators are still valuable, just don't rely on/expect absolute accuracy, nor make assumptions about UI being based on the published API 😀 ... View more

'None' means there is no data, rather than a zero value.   Can you post the exact way you are calling this, all the parameters/values you are using.   Especially the ip parameter, normally use 8.8.8.8 (unless you changed the value in Dashboard config.)   Btw for MX only, I prefer this call as it returns all devices/interfaces in the org... https://developer.cisco.com/meraki/api-v1/get-organization-devices-uplinks-loss-and-latency/   ... View more

Yes, I'd assumed that an MXnnW would count as 'wireless' in this sense.   Haven't any networks with one that don't also have MR devices, maybe someone who does have one can check and confirm? ... View more

Country/region are specific to wireless because of regulatory requirements.   The closest you'll get for generic networks is using... https://developer.cisco.com/meraki/api-v1/get-organization-networks/ ...and the timeZone parameter.   Even with wireless, the only way Dashboard 'knows' what the country it is will be through configuration you input in the first place (auto-detection of wireless country region is absolutely not reliable!)   So if you want to know the country, add it as a tag when configuring the network, then you can always read the tag later - this is what we do.     ... View more

It doesn't say you can search by MAC or IP.   What I see here... https://developer.cisco.com/meraki/api-v1/get-network-client/   Is "Return the client associated with the given identifier. Clients can be identified by a client key or either the MAC or IP depending on whether the network uses Track-by-IP.".   You must give the client key as a mandatory argument, you cannot give MAC or IP. I think the rest could be worded better.   Edit: re-reading, I think it reads ambiguously. I'm also on holiday now, so not really set up for testing, plus it's beer time 🙂 I suggest do a search for the MAC of a current client you know to be active and if it isn't found, open a support case and ask.   As @RaphaelL says, if you want to search by MAC, use the other call, though MAC randomisation may mean some device families are not reliably identifiable this way. ... View more

There's no published API call for this.   There are two early-access API calls that can be used to calculate availability (not differentiated between device/ISP failure, but probability is that mostly it'll be ISP failure rather than device failure)...   Currently we calculate availability across multiple organizations by using this call to log status every 5 minutes, then use the date to calculate availability across the SLA period... https://developer.cisco.com/meraki/api-v1/api-reference-early-access-api-platform-monitor-devices-statuses-get-organization-devices-statuses/     There is a potentially more efficient way using the newer call (I'm not migrating to it unless/until it goes general release)... https://developer.cisco.com/meraki/api-v1/api-reference-early-access-api-platform-monitor-devices-availabilities-changehistory-get-organization-devices-availabilities-change-history/   ... View more

You do need to use both API calls to get all the events, the second one I mention isn't appliance specific, but still is the only way to get certain appliance events that are security related (you can specify a filter so that it will only return appliance events).   These include... {'category': 'Network-Based Application Recognition', 'type': 'nbar_block', 'description': 'Layer 7 firewall rule'} {'category': 'Filtering', 'type': 'cf_block', 'description': 'Content filtering blocked URL'} {'category': 'Filtering', 'type': 'sf_url_block', 'description': 'Security blocked URL'} {'category': 'Filtering', 'type': 'sf_binary_block', 'description': 'Security blocked file'} {'category': 'Intrusion Detection', 'type': 'ids_start', 'description': 'Intrusion detection started'} {'category': 'Intrusion Detection', 'type': 'ids_error', 'description': 'Intrusion detection error'} {'category': 'Intrusion Detection', 'type': 'ids_update', 'description': 'Intrusion detection rules update'}   ...also events for AnyConnect.   This call will get you the current set of possible events, you can see which might be of interest to record... https://developer.cisco.com/meraki/api-v1/get-network-events-event-types/   ... View more

You don't say which API call you are referring to.   I use this for usage analysis, it returns details for each uplink name wan1/wan2/cellular... https://developer.cisco.com/meraki/api-v1/get-network-appliance-uplinks-usage-history/   ... View more

Assume you mean this call...   https://developer.cisco.com/meraki/api-v1/get-organization-appliance-security-events/    It will return up to a year of events. If you use the Meraki Python library it will handle the pagination for you.   Fwiw we gather this data on multiple organizations and store it for analysis/reporting, the call is run monthly for the previous month's events, and results appended to our long-term archive.   There are also non-appliance security events, these are retrieved per-network... https://developer.cisco.com/meraki/api-v1/get-network-events/ ...the events are returned most recent first, so we page until we get to events older than the month before and stop there. ... View more