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 daniel_abbatt
daniel_abbatt
Getting noticed
Member since Dec 9, 2021
Thursday
Community Record
22
Posts
9
Kudos
3
Solutions
Badges
4 weeks ago
Any news on when this can be fixed or an acknowledgement that the issue exists?
... View more
a month ago
https://developer.cisco.com/meraki/api-v1/#!get-organization-config-template-switch-profiles As noted in the WebEx MerakiBot notification: GET `/organizations/{organizationId}/configTemplates/{configTemplateId}/switch/profiles` response has changed response changed from [{'switchProfileId': '1234', 'name': 'A Simple Switch Profile', 'model': 'MS450-24'}] to {'switchProfileId': '1234', 'name': 'A Simple Switch Profile', 'model': 'MS450-24'} This is also reflect in the OpenApi JSON https://raw.githubusercontent.com/meraki/openapi/master/openapi/spec2.json Please revert this change as it is a list that is returned and is incorrectly flagging this as a difference in model compared to OpenApi Schema validation.
... View more
01-10-2023
02:40 AM
It looks like the repo has been fixed in some way as the latest version is 1.29 and no longer 1.30. The release notes still only show 1.28 but the change log now includes 1.29 https://developer.cisco.com/meraki/whats-new/#!v1-29-0
... View more
01-09-2023
01:41 AM
Which version is about to be released? It should be 1.29 I believe, but the repo https://github.com/meraki/openapi is showing 1.30 as being the current release. This repo is supposed to be the source of truth as per https://developer.cisco.com/meraki/api-v1/#!versioning Normally future versions would be on side/beta branches and main would be the current released version. According to the https://github.com/meraki/openapi/releases/tag/v1.29.0 tag, this was released on Jan 4th, but the changelog/release notes don't appear to be updated.
... View more
10-10-2022
06:30 AM
There are a couple of new endpoints in 1.26 which support Appliance inbound cellular firewall rules https://developer.cisco.com/meraki/api-v1/#!get-network-appliance-firewall-inbound-cellular-firewall-rules Is the GET response correct? It's just an array of rules, which in itself is fine, but does not follow the same pattern as the following (along with many other "rules" endpoints) The PUT for the same data https://developer.cisco.com/meraki/api-v1/#!update-network-appliance-firewall-inbound-cellular-firewall-rules The GET for cellularFirewallRules https://developer.cisco.com/meraki/api-v1/#!get-network-appliance-firewall-cellular-firewall-rules The PUT for cellularFirewallRules https://developer.cisco.com/meraki/api-v1/#!update-network-appliance-firewall-cellular-firewall-rules These other endpoints wrap the array in a "rules" property. Can someone at Meraki please either - confirm that the new GET endpoint is correct as documented and is an exception to this pattern, or - confirm that the documentation is incorrect and the actual endpoint behaves like the others
... View more
08-30-2022
12:41 AM
Directed to Meraki API Dev team: I notice this endpoint is per organizationId. Does that mean it can return different results for different organizations? Is it because - the OpenAPI spec doc will include early access/beta endpoints if they are enabled for an organization? - or just an organization endpoint because it logically belongs to an organization? I was under the impression that all organizations ran at the same version of the MerakiApi and therefore the OpenAPI spec JSON would always be the same. Thanks in advance!
... View more
Re: What is the difference between an API wrapper and a SDK
05-12-2022
04:12 AM
05-12-2022
04:12 AM
This rather depends on what your API is to an extent. For a REST API (i.e. not a library/DLL API or similar) then an API wrapper, SDK or API client are all basically the same thing and abstracting away the necessity to manage HTTP calls directly and provide potentially strongly typed parameters and endpoint options. For OS development SDKs can interact with several APIs or even be the API into interacting with the OS or platform.
... View more
04-29-2022
05:15 AM
Ah very nice. I was using https://petstore.swagger.io/ and pasting https://raw.githubusercontent.com/meraki/openapi/master/openapi/spec2.json into the source at the top. Yours looks good though - will investigate.
... View more
04-07-2022
01:47 AM
Could we get some more and clarified documentation on what the new interfaceId is on the Network Appliance VLAN? The response documentation for https://developer.cisco.com/meraki/api-v1/#!get-network-appliance-vlans shows it is a number, but an actual response shows it as a string? Please update the response documentation as I believe it is wrong. I assume this is the unique internal identifier which will can used by other endpoints to uniquely reference a specific VLAN. I think this must be the Ids which are returned by the switch static route endpoint which for IP offset definitions was returning the VLAN unique Id and we never knew which VLAN this was? Please clarify if this is the case. The following endpoints don't show the value in the example but the value is returned - Please update the response documentation to include interfaceId. Please update the documentation for the following responses: https://developer.cisco.com/meraki/api-v1/#!create-network-appliance-vlan https://developer.cisco.com/meraki/api-v1/#!update-network-appliance-vlan
... View more
03-24-2022
02:32 AM
A small caveat to this is that you can of course only retrieve it if you HAVE a network bound to it.
... View more
03-21-2022
12:34 AM
I believe I do understand and agree with what you're saying. That's not the issue I'm having though, can you explain why the same network retrieved via "/networks/nnn" comes back with different values to the same network entry in "/organizations/xxx/networks". To be clear - this is for a Config Template (appliance, switch, wireless) and Network that were just created and bound and the MX then added to the network. I understand the Config Template productTypes could be different from the Network productTypes at this point, but I don't understand why the same Network details retrieved from two different endpoints have different contents - this is unintuitive and so if there is a good reason then the documentation should state it, otherwise it's a bug I believe.
... View more
03-20-2022
12:20 PM
Thanks for the responses and I understand what you're saying. In this case I am simply querying why the networks endpoint returns a different set of productTypes to the network endpoint. The networks endpoint is returning the config template product types whereas the network endpoint is returning the actual network productType. I can't see a reason why they would return different results so without documentation to the contrary, I'll just chalk this one up as a bug in the API response.
... View more
03-19-2022
05:48 AM
https://developer.cisco.com/meraki/api-v1/#!get-network When I make a call to "/networks/nnn" I get the network returned with productTypes that take into account the devices on the network, i.e. with just an MX added, it has the single entry "appliance". {
"id": "N1234",
"organizationId": "xxx",
"name": "Net1",
"productTypes": [
"appliance"
],
"timeZone": "Europe/Amsterdam",
"tags": [],
"enrollmentString": null,
"url": "xxx",
"notes": null,
"configTemplateId": "CT4567",
"isBoundToConfigTemplate": true
} https://developer.cisco.com/meraki/api-v1/#!get-organization-networks The same entry in "/organizations/xxx/networks" shows the productTypes for the Configuration Template that the Network is bound to. In this case it's "appliance", "switch", "wireless". {
"id": "N1234",
"organizationId": "xxx",
"name": "Net1",
"productTypes": [
"appliance",
"switch",
"wireless"
],
"timeZone": "Europe/Amsterdam",
"tags": [],
"enrollmentString": null,
"url": "xxx",
"notes": null,
"configTemplateId": "CT4567",
"isBoundToConfigTemplate": true
} Which is correct and/or why are they different?
... View more
03-17-2022
08:04 AM
So I believe you're saying that there isn't one then as the documentation doesn't define one?
... View more
03-08-2022
02:24 PM
Yup that did it!
... View more
03-08-2022
02:20 PM
2 Kudos
Lol I'm guessing it's the allowLanAccess bool at the root of the request that I just noticed! - I'll try that!
... View more
03-08-2022
02:18 PM
How to Set Local LAN Access Rule Allow/Deny via API? In the UI there is a single dropdown for changing between Allow/Deny, but putting the Layer 3 does not allow modifying the Local LAN Access Rule (as per the documentation). So how can this value be set without going into the UI? https://developer.cisco.com/meraki/api-v1/#!update-network-wireless-ssid-firewall-l-3-firewall-rules
... View more
Labels:
- Labels:
-
SSID
03-07-2022
04:00 AM
3 Kudos
For reference: https://community.meraki.com/t5/Meraki-Service-Notices/Dashboard-connectivity-issues/ba-p/141743#M20
... View more
03-07-2022
03:47 AM
n72 is back again now.
... View more
03-07-2022
03:17 AM
2 Kudos
Appears to be affecting quite a few nodes actually...
... View more
03-07-2022
03:14 AM
2 Kudos
Not getting any response since about 11:00 UK time...
... View more
02-10-2022
12:40 PM
Yes, that's all we can go on. Unfortunately it's not very comprehensive in terms of possible return values for things like enums etc.
... View more
My Accepted Solutions
| Subject | Views | Posted |
|---|---|---|
| 199 | 01-10-2023 02:40 AM | |
| 751 | 03-21-2022 12:34 AM | |
| 551 | 03-08-2022 02:20 PM |
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 3 | 5646 | |
| 2 | 551 | |
| 2 | 6768 | |
| 2 | 6850 |
