I suggest post on the EA group that you are interested in this feature and would like to help with testing/feedback if possible.   On other EA calls there has been opportunity to do this. ... View more

You can make a feature request in Dashboard.   Otherwise, your options are to contact your Cisco/Meraki account manager(s).   Tbh it sounds like CC is where the issue is, so you could also try opening a support case on CC. ... View more

I recently opened a case regarding the "null" response to the user creation. Looks like any uppercase letter in the email creates this behaviour. Sending the email variable as email.lower() resolves the issue. Note that in all cases (sending uppercase letters or not), the resulting created user's email is always lowercase in the dashboard. ... View more

Thanks to @John_on_API  this did the trick for me. Below is the final code. Hope its useful to others to adapt as they see fit.     # Script to retrieve Meraki AP info from all networks from all org the API key has access to #All Switches and AP devcies name are assumed to start with AP* or SW* from datetime import datetime import os import meraki import pandas as pd # Meraki API Key name that is retrieve from the OS environment variable. MERAKI_DASHBOARD_API_KEY_NAME = 'MERAKI_API_KEY' # Readonly key #Set CSV / XLXS folder path to the output folder under the script output_path = f"{os.path.dirname(__file__)}/output" def extract_ap_details(linkLayerDevices_response, site_name, org_name): """ Extract access point details from the 'links' node of the given response. Strips "Port " from portId to get only the port number, renames field to 'port_number', and includes additional parameters 'site_name' and 'org_name'. Parameters: linkLayerDevices_response (dict): The response dictionary containing 'links' node. site_name (str): The name of the site where the devices are located. org_name (str): The name of the organisation. Returns: list: A list of dictionaries containing details of switches, access points, and metadata. """ ap_details = [] # Safely get the 'links' list from the response links = linkLayerDevices_response.get("links", []) if not isinstance(links, list): return ap_details # Return empty list if 'links' is not a list # Iterate through each link in the list for link in links: ends = link.get("ends", []) if not (isinstance(ends, list) and len(ends) == 2): continue # Skip if 'ends' is not a list of exactly 2 dictionaries # Extract potential switch and access point nodes switch = ends[0] access_point = ends[1] # Validate the "SW" and "AP" naming conventions sw_device = switch.get("device", {}) ap_device = access_point.get("device", {}) sw_name = sw_device.get("name", "") ap_name = ap_device.get("name", "") if not sw_name.startswith("SW"): continue # Skip if the device name does not start with "SW" if not ap_name.startswith("AP"): continue # Skip if the second device name does not start with "AP" # Extract additional details with safe fallbacks sw_discovered = switch.get("discovered", {}) sw_lldp = sw_discovered.get("lldp") or {} # Default to empty dict if None sw_cdp = sw_discovered.get("cdp") or {} # Default to empty dict if None # Extract and clean port number port_id = sw_lldp.get("portId", "").replace("Port ", "").strip() # Append the validated data into the result list ap_details.append({ "ap_name": ap_name, "ap_serial": ap_device.get("serial", ""), # Default to empty string if missing "sw_name": sw_name, "sw_serial": sw_device.get("serial", ""), # Default to empty string if missing "sw_port_number": port_id, # Cleaned port number "sw_port_native_vlan": str(sw_cdp.get("nativeVlan", "")), # Default to empty string if missing "site_name": site_name, # Added site_name "org_name": org_name # Added org_name }) return ap_details def main(): if MERAKI_DASHBOARD_API_KEY_NAME in os.environ: print(f"API Key Environment variable [{MERAKI_DASHBOARD_API_KEY_NAME}] found.") else: print(f"API Key Environment variable [{MERAKI_DASHBOARD_API_KEY_NAME}] Does not exists!") exit(1) MERAKI_DASHBOARD_API_KEY = os.getenv(MERAKI_DASHBOARD_API_KEY_NAME) # Get the actual Meraki API Key # Start a Meraki dashboard API session try: print(f"\nTrying to connect to Meraki API Using [{MERAKI_DASHBOARD_API_KEY_NAME}]") dashboard = meraki.DashboardAPI( api_key=MERAKI_DASHBOARD_API_KEY, base_url='https://api.meraki.com/api/v1/', print_console=False, output_log=False, suppress_logging=True, wait_on_rate_limit=True, maximum_retries=100 ) except meraki.APIError as e: print("Unable to connect to Meraki API.") print(f'Meraki API error: {e}') print(f'status code = {e.status}') print(f'reason = {e.reason}') print(f'error = {e.message}') else: # Get list of organizations to which the supplied API key has access to. organizations = dashboard.organizations.getOrganizations() organizations = sorted(organizations, key=lambda x: x['name']) # Sort Org by name # Print name of the Orgs found print(f"Found: [{len(organizations)}] organisations.") for org in organizations: print(f"{org['name']}") # Iterate through list of Orgs and gather details we need all_org_ap_info = [] # Store all the networks in all orgs so we can write to a file later. for org in organizations: org_id = org['id'] # Save ID name for use later org_name = org['name'] # Save Org name for use later print(f"\nAnalysing organization {org_name}:") # Get list of networks in current organization try: org_networks = dashboard.organizations.getOrganizationNetworks(org_id) except meraki.APIError as e: print(f'Meraki API error: {e}') print(f'status code = {e.status}') print(f'reason = {e.reason}') print(f'error = {e.message}') continue except Exception as e: print(f'some other error: {e}') continue # Skip error in current Meraki network #We are only interested in neworks where there is a Switch AND wireless print(f"\n[Org:{org_name}] Filtering Meraki network type to those that has a Switch & Wireless") # Use list comprehension to filter the list networks = [ network for network in networks if "switch" in network["productTypes"] and "wireless" in network["productTypes"] ] # Sort List of network by name print(f"\n[Org:{org_name}] Sorting network list by alphabetical order") networks = sorted(networks, key=lambda x: x['name']) # Iterate through networks in current organisation total = len(networks) # count number of Meraki networks counter = 1 # Keep count of number of network as we iterate through them. print(f'Iterating through {total} networks in organization in {org["name"]} to get list of APs information') # Loop through the list of networks and retrieve the needed info for network in networks: # Create a new list of dictionaries to store AP info network_ap_info = [] network_name = network["name"] #get this Network Link Layer devices info which contains the SW LLDP & AP info we need linkLayerDevices_response = response = dashboard.networks.getNetworkTopologyLinkLayer(network["id"]) #retrieve the APs infor for this network network_ap_info = extract_ap_details(linkLayerDevices_response, network["name"], org_name) # Sort the list by the "ap_name" key using list comprehension network_ap_info = sorted(network_ap_info, key=lambda x: x["ap_name"]) #Combine the curent org network info into the all_org dict for later use all_org_ap_info = network_ap_info + all_org_ap_info print(f"Gathering AP info for Org:[{org['name']}] Network:[{network_name}] completed.") print(f"Gathering info for Org:[{org['name']}] completed.") df_all_org_ap_info_info = pd.DataFrame(all_org_ap_info) # # write the DataFrame to a CSV file current_datetime = datetime.now().strftime("%Y-%m-%d %H-%M-%S") filename = f"{output_path}/all_orgs_ap-_info--{current_datetime}.xlsx" df_all_org_ap_info_info.to_excel(filename) print(f"Exported filename: {filename}") print(f"NOTE: APs without a Switch port number are offline or dormant.") if __name__ == "__main__": # Call Main to do all the actual work. start_time = datetime.now() main() end_time = datetime.now() print(f'\nScript complete, total runtime {end_time - start_time}')     ... View more

Sungod,    Thank you so much for your assistance! ... View more

Hi, I have code that does this. Please feel free to use. It only pulls up APs, but it can be changed for switches and other. Also on this page, I have something called, "ListNetworkStarterCode," that will help you take the org and list the network.  Merakicode/APs&Ser_PerNetwork at main · jadexing/Merakicode I have a lot on github for Meraki. Please help yourself. I've been working at bettering old code and putting a good description of which APIs are referenced and what the code does. ... View more

I've been looking at how to replicate our existing reporting/analytics without polling using getOrganizationDevicesStatuses but it's not straightforward...   The replacements don't include publicIP, which is useful for simply inferring whether it's a single device outage, or one where a device/WAN/other failure is taking out multiple devices.   I don't see another simple way to get the publicIP, calls that get it for MX/Z are no use as not all devices are behind an MX/Z.   Am I missing an easy way to get publicIP? If not, can it be added at least to the replacement operation getOrganizationDevicesAvailabilities it shouldn't break anything.   Also, one of our main use cases is contractual SLA analysis/reporting, which typically is calendar month, sometimes also by local timezone.   I'd certainly like to move from our current polling approach to a monthly one, but for that a lookback of at least a couple of days more than 31 days is needed to allow for timezones and any transient problems that delay colection, otherwise we lose data.    The https://developer.cisco.com/meraki/api-v1/get-organization-devices-availabilities-change-history/ documentation says has a maximum lookback of 2678400, exactly 31 x 24 x 60 x 60, meaning that unless we ran it at 235959 on the last day of the month for each timezone, it's possible to lose visibility.   In practice we run 'monthly' data gathering early UTC on the 2nd of the following month, simply allowing for where we need to report by local timezone and to giving some buffer in case of a problem.   The 'easy' way out would be to run it daily instead of monthly, but IMHO it'd be better if this and other calls with one-month lookback hard limits were extended by a couple of days to fit better with the common customer desire to have monthly reports and the need for a bit of contingency 😀 ... View more

Not a good fix, but potentially if desperate enough you could consider restricting API access to a set of IP addresses until the core issue is resolved.     ... View more

The MT12 leak detector might work.   It presumably works by sensing the change in current through the sensor cable, so I'd think you could use it as an open/closed detector. ... View more

Just a fyi for anyone seeing similar, the issue has bubbled through the layers of support and is now with the Meraki engineering team.   ... View more

Thanks for additional responses to this. I've been tied up on a few other things but will take a look at suggestions and reply accordingly! ... View more

As soon as i make the get network APi call, it seems that its ready, however from the result that the API provides theres no status field, that tells you if its ready or not.  If i get a valid response from the get network api does this mean that it is ready?   I've wrapped it in a try except, but as it turns out i'm not getting a failure.. If i go create nework, then claim device it always fails..  but  create network,  get network, claim device. well that works. It woudl be nice if there was a status property ... View more

I'm not sure how closely those numbers should align, because I'm not familiar with the methods that produce the data. But it is something that you can review with Support, if you're interested.   If you're comparing API with GUI, then you'll need to make sure that you're using the same timespan controls on the API as on the GUI, and it's possible that you'll need to map timezones if you want them to line up (API uses UTC, org-wide data in GUI typically uses UTC, network-specific data in GUI often uses the network's configured timezone). ... View more

Congratulations @thomasthomsen ! ... View more

This was the response we got: "In high-density environments with numerous gateways, sensors may frequently switch between them. This is expected behaviour, though future updates are expected to improve it. Unfortunately, there is no way to prevent this behavior at the moment"   Our issue isn't gaps in data though, but constant alerts that the sensors aren't connecting to access points far away from them even though they have at least 1 acceptable connection.  We have mt10s and mt12s very close to each other and only have this issue with the MT 12s. MT 12:   MT 10:     Both are showing yellow connections with not the greatest RSSI but we have only seen the MT12s alert not the MT 10s.   Or maybe I'm missing something and just need to move the MT12s. ... View more

Do bear in mind that 'read-only' access is not totally read-only - a read-only account still allows port-cycling and cable-test operations to be performed on switch ports.   For instance, cycling a port will result in downstream devices will losing connectivity and PoE.   We had a customer find this out the hard way.   I.e. you still need to be careful about granting read-only permission and caution users about these operations. ... View more

You have...   perPage='1000',   ...but this should be an integer, try...   perPage=1000,   Otherwise, assuming the equipment has been installed and with current config before 1st September, if there were security events they should be there.   One other thing to try, just in case something weird is going on, add the parameter...   sortOrder='descending'   ...and see if it makes a difference to what you get.   If it's still not working, you may need to open a support case. ... View more

Congrats @sungod  I remember when I joined the community I thought there was no way I was ever going to achieve that level so congrats, it's an achievement well worth celebrating.  ... View more

Update your URL variable to include '?perPage=5000' or whatever number you're looking for. E.g.  "https://api.meraki.com/api/v1/organizations/$orgID/networks?perPage=5000" ... View more

You are right, adapting from javascript to python is pretty easy. I think it would be beneficial to use the library for api calls instead of regular http calls in javascript where we would lack all the parameters the library offers ... View more

Please do report this to support. ... View more

The first and third look ok, the middle one is no good as the serial numbers aren't a positional parameter, they're a keyword argument.   Any chance you fell foul of the special rate limit on the endpoint? "This operation can be used up to ten times within a single five minute window."   Otherwise, maybe it's just another transient weirdness 😀 ... View more

getOrganizations is open to every user to find out what they have some degree of access to.   Whereas getOrganizationSaml targets a specific org ID, so you need to have org access to use it.   If you have readonly access, you can only GET.   If you have read-write, you can use all request types, PUT, POST etc.   See... https://documentation.meraki.com/General_Administration/Other_Topics/Cisco_Meraki_Dashboard_API   ... View more