- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Postman Collection - Updates and a little polish
Meraki Postman Collection Updates
What's New?
The Meraki Postman Collection is now built with our OpenAPI v3 specification!
Taking advantage of our new OASv3 specification for the Dashboard API, we've been able to give our Postman Collection some love.
Navigation changes
We've improved the overall navigation tree to better align with the official API Docs.
- General folder renamed to platform
- Administered folder moved from products to platform
- This folder contains administrative functions outside of the organization and not related to any specific product
- Requests are now listed by operationId instead of their description.
- Developing with an SDK often uses the operationId and being able to search on that should make it easier to find the resource you need.
New Format
| Old Format
|
Bearer authentication
- Adopting industry standards and setting the Authorization header to Bearer Token.
(learn more about Meraki API Auth here)
Follow Authorization header redirect settings
- Set to off as default. this is no longer required for Dashboard API v1 and will improve the security of the collection.
Bug fixes
- Collection Variables have been simplified to only include the baseUrl. Personal environments can be leveraged to define additional variables.
We hope you find the new updates helpful. Let us know in the comments.
Learn more
Meraki Postman Docs
Dashboard API v1 Collection
- Labels:
-
Dashboard API
-
Updates from Meraki
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Great updates in this release!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I, for one, am a huge fan of these changes. So much easier to find the endpoint I want!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hey Fam - Just made the switch from custom header to bearer token in postman... i have to enable the "follow authorization header" setting in every request i have tested. Is there a way to enable this globally or for the entire collection?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This should be the default for the Postman collection (Bearer Token and {{apiKey}}). I have the apiKey variable set in my Environment. I never have to do anything else.
Perhaps there are other methods too?
