Postman Collection - Updates and a little polish

DexterLaBora
Meraki Employee
Meraki Employee

Postman Collection - Updates and a little polish

 

Meraki Postman Collection Updates

 

DexterLaBora_6-1694092555311.png

 

What's New?

The Meraki Postman Collection is now built with our OpenAPI v3 specification!

 

 

DexterLaBora_0-1694092411610.png

 

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


DexterLaBora_1-1694092411570.png

 

Old Format


DexterLaBora_2-1694092411740.png

 

 

 

Bearer authentication

  • Adopting industry standards and setting the Authorization header to Bearer Token.
    (learn more about Meraki API Auth here)
    DexterLaBora_3-1694092411545.png

 

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.

DexterLaBora_4-1694092411553.png

 

Bug fixes 

  • Collection Variables have been simplified to only include the baseUrl. Personal environments can be leveraged to define additional variables.
    DexterLaBora_5-1694092411583.png

     

 

We hope you find the new updates helpful. Let us know in the comments.

 

 

Learn more
Meraki Postman Docs

Dashboard API v1 Collection

 

4 Replies 4
Ryan_Miles
Meraki Employee
Meraki Employee

Great updates in this release!

Ryan

If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.
John_on_API
Meraki Employee
Meraki Employee

I, for one, am a huge fan of these changes. So much easier to find the endpoint I want!

Craig_Egan
Meraki Employee
Meraki Employee

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? 

Ryan_Miles
Meraki Employee
Meraki Employee

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?

Screenshot 2024-04-23 at 15.41.23.png

Ryan

If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.
Get notified when there are additional replies to this discussion.