Meraki

seanmathias · ‎Sep 21 2021

Has anyone had success with this endpoint? I have not been able to get a valid response, and am instead getting 404. I have plenty of other scripts that are able to access API endpoints via requests, but this one fails. My network is enabled for beta features, and I am using the specific shard rather than the generic api.meraki.com, but no luck.

seanmathias · ‎Mar 26 2021

@AlexAndorko Unfortunately, no, this is one of *many* things that are visible in Dashboard but are not exposed via any API endpoint. I keep holding out hope that they will start to publish more endpoints and close this gap, as it would be very helpful for some of us, but so far not much progress.

seanmathias · ‎Nov 30 2020

Got it, thanks for the response Donovan

seanmathias · ‎Nov 30 2020

I know there have been similar threads in the past to this, but given that there are now 3 different MX security license levels, I thought it was relevant and worth asking again. Is there an API endpoint in to determine the MX license level for an Organization? Ideally it would be a single endpoint whether PDL or co-term (that logic can be handled in the backend I would think), or is there one in the works? Though this can be determined via /organizations/{organizationId}/licenses for PDL organizations, this does not cover co-term Orgs. It would make sense to provide this single data point at the Organization level as all MX appliances in the Org have to be licensed at the same level.

seanmathias · ‎Nov 25 2020

I am not so sure about that, or at least I don't know if that is a complete answer. It may be that is the case when support pins a device to a specific firmware version, but I am getting this response from multiple devices that are new out of the box and have never had intervention by support. It would also be nice if the /organizations/{organizationId}/devices endpoint was consistent in what it returns for the firmware field. Sometimes it returns the firmware release, which is expected, other times it returns this status message. I would say from a usability perspective it should just return the running firmware release. @Meraki - Any insight would be appreciated!

seanmathias · ‎Nov 20 2020

Hello Team Meraki, Has an endpoint been added to Dashboard to get/set the MX mode (routed or VPN/passthrough)? To @BreckanM point, this would be a really useful check to be able to use to determine other script logic based on the role of the MX.

seanmathias · ‎Nov 11 2020

That is not actually part of the DashboardAPI, but is actually part of the Python SDK. What you found are the docs essentially, there is no SDK specific documentation that I am aware of. The specific flag you are looking for is 'suppress_logging'.

seanmathias · ‎Sep 2 2020

I know this is an older episode, and so much has happened and changed since it aired...but they brought up the idea of an IOS like CLI for Meraki... I know this makes no sense really, and could be seen as counter-productive, allowing people to cling to old ways of working...but this is an idea I have had too many times myself, and it appeals to my inner keyboard-jockey. I don't see how I CAN'T do this now...GitHub repo to follow 😉

Meraki

Community

About seanmathias

seanmathias

API Early Access Group

Community Record

Badges

Re: IN BETA: Link-layer network topology

Re: detect MX in passthrough mode via API?

Re: Determine Organization MX license level

Determine Organization MX license level

Re: Query on "API calls to Meraki demo environment"

Re: detect MX in passthrough mode via API?

Re: Options for DashboardAPI()?

Re: Episode 6: Evolving IT experiences with APIs

Re: Episode 6: Evolving IT experiences with APIs