Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Register or Sign in
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About Prodrick
Prodrick
Building a reputation
Member since Nov 13, 2022
3 hours ago
Community Record
83
Posts
18
Kudos
1
Solution
Badges
Mar 8 2024
12:50 PM
Ok, I got this working, but I don't know why the following command did not give me an incorrect API key response when I missed a character. Thanks to all who helped.
... View more
Mar 8 2024
12:38 PM
I literally copied the curl command from this page, and followed the same process as I usually to to test endpoints. I copy the curl example, swap-out my API key and put single quotes around the call. I'm used to the API providing a useful error message, but in this case I get nothing. https://developer.cisco.com/meraki/api-v1/get-network-events/
... View more
Mar 8 2024
12:04 PM
I think the post stripped that out. Here's a screenshot. No error message, just a null response. Could there be something a customer has to enable in the Dashboard that I could verify via the API?
... View more
Mar 8 2024
11:39 AM
Thanks so much. When I execute this for a network that I know has an appliance, this is what I get: Last login: Fri Mar 8 13:50:23 on ttys000 patrick.rouse@RMT-PROUSE ~ % curl -L --request GET \ --url 'https://api.meraki.com/api/v1/networks/L_1234567890/events?productType=appliance' \ --header 'Authorization: Bearer 1234567890\ --header 'Accept: application/json' patrick.rouse@RMT-PROUSE ~ %
... View more
Mar 8 2024
10:59 AM
I've been trying to use this endpoint but haven't had any success. I wonder if someone might share a working example executed with curl.
... View more
Feb 8 2024
3:16 PM
This is what that returns for an example network with two appliances: curl -L --request GET \ --url 'https://api.meraki.com/api/v1/organizations/OrgId/uplinks/statuses' \ --header 'Authorization: Bearer ApiKey' \ --header 'Accept: application/json' [ {"networkId":"L_XXXX5794224244XXXX","serial":"Q2JN-229D-XXXX","model":"MX100","highAvailability":{"enabled":true,"role":"primary"},"lastReportedAt":"2024-02-08T23:05:07Z","uplinks":[ {"interface":"wan1","status":"active","ip":"203.XXX.42.110","gateway":"203.220.42.109","publicIp":"203.XXX.42.110","primaryDns":"1.0.0.1","secondaryDns":"8.8.8.8","ipAssignedBy":"static"}, {"interface":"wan2","status":"ready","ip":"10.0.100.5","gateway":"10.0.100.1","publicIp":"1.XXX.1.161","primaryDns":"1.0.0.1","secondaryDns":"8.8.8.8","ipAssignedBy":"dhcp"}]}, {"networkId":"L_XXXX5794224244XXXX","serial":"Q2JN-2UKG-XXXX","model":"MX100","highAvailability":{"enabled":true,"role":"spare"},"lastReportedAt":"2024-02-08T23:05:09Z","uplinks":[ {"interface":"wan1","status":"active","ip":"10.0.100.4","gateway":"10.0.100.1","publicIp":"1.XXX.1.161","primaryDns":"1.0.0.1","secondaryDns":"8.8.8.8","ipAssignedBy":"dhcp"}, {"interface":"wan2","status":"not connected","ip":null,"gateway":null,"publicIp":null,"primaryDns":null,"secondaryDns":null,"ipAssignedBy":null}] }
... View more
Feb 8 2024
2:50 PM
Thanks. I made calls to both endpoints, and I think I follow you now. However, the vlans endpoint returns applianceIp, but no serial field. How might one resolve which of the two (primary/secondary) appliances this applianceIp belongs to?
... View more
Feb 8 2024
2:14 PM
This is the response I get for the first MX. Given this response, how might I determine the lanIp? Thanks. curl -L --request GET \ --url 'https://api.meraki.com/api/v1/organizations/OrgId/devices/statuses' \ --header 'Authorization: Bearer ApiKey' \ --header 'Accept: application/json' [ {"name":"XXXX-XXX-MX1", "serial":"XXXX-XXXX-6599", "mac":"XX:XX:XX:XX:68:68", "publicIp":"203.XXX.42.110", "networkId":"L_69805794224244XXXX", "status":"online", "lastReportedAt":"2024-02-08T22:03:05.007000Z", "productType":"appliance", "components":{"powerSupplies":[]}, "model":"MX100", "tags":[], "usingCellularFailover":false, "wan1Ip":"203.XXX.42.110", "wan1Gateway":"203.XXX.42.109", "wan1IpType":"static", "wan1PrimaryDns":"1.0.0.1", "wan1SecondaryDns":"8.8.8.8", "wan2Ip":"10.0.100.5", "wan2Gateway":"10.0.100.1", "wan2IpType":"dhcp", "wan2PrimaryDns":"1.0.0.1", "wan2SecondaryDns":"8.8.8.8"}
... View more
Feb 8 2024
1:37 PM
When getting the list of devices for a given org from the following endpoint, appliances include the wan1Ip and wan2Ip, but not the lanIp. However, for devices like cameras and wireless, this endpoint provides the lanIp. I need a way to get the lanIp of appliances, so when I add them to my monitoring platform the it can contact the devices on an internal IP. Thoughts on how one might programmatically get the lanIp for MX Security Appliances? Thanks. curl -L --request GET \ --url 'https://api.meraki.com/api/v1/organizations/OrgId/devices' \ --header 'Authorization: Bearer ApiKey' \ --header 'Accept: application/json'
... View more
Feb 8 2024
11:27 AM
We include both methods just in case
... View more
Feb 3 2024
6:58 PM
This is great, it’s just an expensive API call in large environments.
... View more
Feb 3 2024
1:41 PM
So, one might deduce that any other ports returned by snmp.meraki.com are WAN Ports? Is there any API endpoint that returns Appliance interface traffic stats (send/receive bytes), or is snmp.meraki.com or local SNMP the only way?
... View more
Feb 3 2024
12:31 PM
1 Kudo
Interestingly, there is an endpoint that gets non WAN ports. Hmmm. Maybe one could make this call and assume the others are the WAN ports? This should not be so difficult. Example: curl -L --request GET \ --url 'https://api.meraki.com/api/v1/networks/[Network_ID Here]/appliance/ports' \ --header 'Authorization: Bearer [API Key Here]' \ --header 'Accept: application/json' [ {"number":3,"enabled":true,"type":"access","dropUntaggedTraffic":false,"vlan":10,"accessPolicy":"open"},{"number":4,"enabled":true,"type":"trunk","dropUntaggedTraffic":true,"allowedVlans":"all"},{"number":5,"enabled":true,"type":"trunk","dropUntaggedTraffic":true,"allowedVlans":"all"},{"number":6,"enabled":true,"type":"trunk","dropUntaggedTraffic":true,"allowedVlans":"all"},{"number":7,"enabled":true,"type":"trunk","dropUntaggedTraffic":true,"allowedVlans":"all"},{"number":8,"enabled":true,"type":"trunk","dropUntaggedTraffic":false,"vlan":11,"allowedVlans":"10,11"},{"number":9,"enabled":true,"type":"trunk","dropUntaggedTraffic":false,"vlan":11,"allowedVlans":"10,11"},{"number":10,"enabled":true,"type":"trunk","dropUntaggedTraffic":true,"allowedVlans":"all"},{"number":11,"enabled":true,"type":"trunk","dropUntaggedTraffic":true,"allowedVlans":"all"} ]
... View more
Feb 3 2024
9:21 AM
Thanks @Ryan_Miles . Ultimately what I am trying to get is the status, loss and latency (which I get with the org-level uplink endpoints) and match them up with the send/receive traffic. In most cases it’s easy to match the API data with the WAN interface data I get via snmp.meraki.com, but I’m unaware of an infallible method. ideally, there would be a single org level endpoint that would provide the lloss, latency, send, and receive traffic for each WAN interface. Without this I am relegated to matching up API data and snmp data which is challenging. So, if there were an endpoint I could call to reliably get the interface (port) numbers for WAN1 and WAN2 I’d be good to go. alternatively, I’d be delighted for an API solution but it can’t be like switches where I have to query by serial number because that doesn’t scale. Does that make sense?
... View more
Feb 2 2024
8:14 PM
What Dashboard API endpoint will help to positively identify which ports (interfaces) are configured as WAN1 and WAN2? An example device in the MX105 thanks
... View more
Jan 28 2024
1:34 PM
I suppose we’ll find out in a few days. I’m referring to this specific statement: ”check that your API call has the correct header with the following (and not v0's X-Cisco-Meraki-API-Key) Authorization: Bearer {API_KEY}“
... View more
Jan 28 2024
12:58 PM
I am aware that v0 end of life is this week, I'm asking more about this specific authentication method that worked for v0 and v1.
... View more
Jan 28 2024
12:17 PM
Is it a correct assumption that this v0 authentication method will cease to function on Thursday, February 1st, even if using this method with v1 endpoints? X-Cisco-Meraki-API-Key Reference: (Troubleshooting Section) https://developer.cisco.com/meraki/api/authorization/#obtaining-your-meraki-api-key
... View more
Jan 28 2024
8:06 AM
Thanks so much! I was surprised that deviceSerial was not included like it is for network events. https://api.meraki.com/api/v1/networks/:networkId/events
... View more
Jan 28 2024
7:22 AM
Is the deviceMac in this response the hardware address of the Security Appliance? https://developer.cisco.com/meraki/api/get-organization-appliance-security-events/ {
"ts": "2018-02-11T00:00:00.090210Z",
"eventType": "IDS Alert",
"deviceMac": "00:18:0a:01:02:03",
"clientMac": "A1:B2:C3:D4:E5:F6",
"srcIp": "1.2.3.4:34195",
"destIp": "10.20.30.40:80",
"protocol": "tcp/ip",
"priority": "2",
"classification": "4",
"blocked": true,
"message": "SERVER-WEBAPP JBoss JMX console access attempt",
"signature": "1:21516:9",
"sigSource": "",
"ruleId": "meraki:intrusion/snort/GID/1/SID/26267"
}
... View more
Dec 7 2023
8:40 PM
2 Kudos
@alemabrahao thanks for causing me to not be lazy and to look a little deeper. I found the following per-network endpoint to provide what I was looking for. I started with no filters and the default timespan of 1 day, but this gets just Wireless clients for the past hour and provides the per-Wireless client data usage for the related SSID and AP. With this I can group and sum the data per AP and per SSID. https://developer.cisco.com/meraki/api/get-network-clients/ I wish this were a per Org Call so I could get it more often or if the syslog would write the SSID connection information, so I could get this without any API calls. Please let me know if you/anyone might know of a more API efficient way to get this information. Thanks again. curl -L --request GET \ --url 'https://api.meraki.com/api/v1/networks/[networkId]/clients?timespan=3600&recentDeviceConnections[]=Wireless' \ --header 'Authorization: Bearer [API Key]' \ --header 'Accept: application/json' Example response for one of the many clients (I anonymized the Client PII) { "id":"abc123", "mac":"[Client MAC ]", "description":"[Client Description]", "ip":"[Client IPv4 Address]", "ip6":null,"ip6Local":"[Client IPv6 Address]", "user":null, "firstSeen":"2023-12-07T18:14:25Z", "lastSeen":"2023-12-08T04:15:21Z", "manufacturer":null, "os":"Apple iPhone", "deviceTypePrediction":null, "recentDeviceSerial":"[Meraki AP Serial Number]", "recentDeviceName":"[Meraki AP Name]", "recentDeviceMac":"[Meraki AP MAC]", "recentDeviceConnection":"Wireless", "ssid":"[SSID Name]", "vlan":"28", "switchport":null, "usage":{"sent":791,"recv":1470,"total":2261}, "status":"Online", "notes":null, "groupPolicy8021x":null, "adaptivePolicyGroup":null, "smInstalled":false, "namedVlan":null, "pskGroup":null}, }
... View more
Dec 7 2023
5:43 PM
I’d like to be able to get the current client count for a given AP grouped by SSID Name. Thoughts on which API endpoints might provide this info?
... View more
Dec 6 2023
7:43 PM
Thanks so much. This is what the default response looks like: curl -L --request GET \ --url 'https://api.meraki.com/api/v1/networks/[Network_ID]/appliance/uplinks/usageHistory' \ --header 'Authorization: Bearer [API_KEY]' \ --header 'Accept: application/json' [{"startTime":"2023-12-07T03:28:00Z","endTime":"2023-12-07T03:29:00Z","byInterface":[{"interface":"wan1","sent":247563,"received":332677}]},{"startTime":"2023-12-07T03:29:00Z","endTime":"2023-12-07T03:30:00Z","byInterface":[{"interface":"wan1","sent":261868,"received":250274}]},{"startTime":"2023-12-07T03:30:00Z","endTime":"2023-12-07T03:31:00Z","byInterface":[{"interface":"wan1","sent":190085,"received":238026}]},{"startTime":"2023-12-07T03:31:00Z","endTime":"2023-12-07T03:32:00Z","byInterface":[{"interface":"wan1","sent":394777,"received":448573}]},{"startTime":"2023-12-07T03:32:00Z","endTime":"2023-12-07T03:33:00Z","byInterface":[{"interface":"wan1","sent":313629,"received":365290}]},{"startTime":"2023-12-07T03:33:00Z","endTime":"2023-12-07T03:34:00Z","byInterface":[{"interface":"wan1","sent":181944,"received":213173}]},{"startTime":"2023-12-07T03:34:00Z","endTime":"2023-12-07T03:35:00Z","byInterface":[{"interface":"wan1","sent":376337,"received":432645}]}
... View more
Dec 6 2023
2:58 PM
The only endpoints I am aware of are the Uplink Loss and Latency and the Uplink Status, which if my memory serves me do not provide port/interface or send/receive data.
... View more
Dec 6 2023
2:35 PM
I’m already exporting Netflow/IPFIX but not via API. Which endpoint were you referring to? Thanks so much.
... View more
My Accepted Solutions
| Subject | Views | Posted |
|---|---|---|
| 523 | Dec 7 2023 8:40 PM |
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 2 | 523 | |
| 2 | 670 | |
| 2 | 840 | |
| 2 | 932 | |
| 1 | 3777 |
© 2024 Cisco Systems, Inc.
