Includes all dashboard API updates offered in version 1.22 and prior. This patch update includes the following enhancements: A security fix for a path variable injection vulnerability. While at this time there are no known instances of this being used in an attack, a malicious user who had access to another application developed using this library could theoretically cause unexpected behavior with that application. It's highly recommended that all developers update to 1.22.1 or later, which addresses this issue by sanitizing path parameter input. Support for the 'administered' scope Support for endpoints that enable interaction with Early Access features   Upgrade with :   pip install --upgrade meraki   API changelog: https://developer.cisco.com/meraki/whats-new ... View more

Includes all dashboard API updates offered in version 1.22 and prior.    Upgrade with :   pip install --upgrade meraki   API changelog: https://developer.cisco.com/meraki/whats-new ... View more

As you've heard, API v0 has been deprecated since August 2020, and sunset as of February 5. If you are still using API v0, you are at risk, and should migrate your operations to v1 endpoints at your first opportunity.   To assist with this, we’ve just released a new feature for our getOrganizationApiRequests endpoint that makes it trivial for customers to identify API v0 usage. To use it with this endpoint, call the endpoint with the new version query param:   GET /organizations/:organizationId/apiRequests?version=0   This new filter ?version=0 is live, but not yet added to documentation (expect the docs update in June). Using this query parameter, the endpoint will only return requests made to API v0 endpoints for the given timespan. It will return an empty set [] if there were no API v0 requests made for that organization for the given timespan.   We hope you will find this helpful during your migration from API v0 to v1! ... View more

What is the Early Access program? The early access program (also known as our beta program) enables you to beta test APIs before they are finalized. This is the best opportunity to weigh in on features and functionality before we finalize the UX and ship (GA) the endpoints. Find more information in the original announcement, or the documentation page.   How does the Early Access program work? First, an organization admin would choose an organization to opt in to the program, and once opted in, the OpenAPI spec for that organization will be changed to the beta spec. That means all API users interacting with that organization will have immediate access to the current beta features. And as soon as new features are released to beta, you can immediately use them with your organization and provide feedback in our Early Access group, so you'll want to inform all API users of this change before signing up.   Technically, joining also means that all endpoints in the given org's OpenAPI spec are subject to unannounced breaking changes, so it's not for everyone. In other words, once an org is opted in, every API user is now subject to the beta API spec, so choose your organization thoughtfully.   New features are published in our Early Access streaming live updates Webex channel and occasionally will be called out in the community's API Early Access Group.   Should I join the Early Access program? Only you can decide, but here are a few questions to ask yourself before joining: Am I a read-write organization admin on the organization I want to opt into the program? Am I authorized to make this change for my organization? Do all API users of my organization understand the impacts of joining the program, and that joining the program might break any/all applications that depend on the API? Are breaking API changes acceptable for all API users (including ecosystem partners) who interact with my organization and all its networks? Do I want to provide feedback on beta API features before they are shipped? If you answered "Yes" to all of the above, then you may be a candidate for the program! Again, joining the program is on a per organization basis, so if you're interested, we recommend creating a separate testing organization rather than joining your production organization(s) to the program.    Are there any active betas right now? Yes! There are virtually always active betas available for testing and experimentation.   How do I join or leave the program? We've made it easier than ever to participate in the early API access program! Previously, it was necessary to allow Support to access your dashboard, and then to make a special request to have the opt-in applied to your organization, and leaving the program for an org required contacting support. No more!   Now to participate simply log in to your dashboard, choose the organization you'd like to opt in or out of the beta, then use the opt-in toggle to opt-in your organization to the program. Once opted in, you'll instantly have access to all the current beta API endpoints.   And yes! This toggle is fully API-powered, so you can turn this on and off via API if you please.         ... View more