Postman authorization for v1

Ritor
Conversationalist

Postman authorization for v1

Hi All,

 

Need your help.

I worked with API before, but never had such an issue with authorization.

I'm having the following error: 401 Authorization required

My actions:

Forked the 1.47 collection to my Postman.

Generated API key for organization.

Checked that API Access enabled for the Org.

Postman:

Keep the collection Authorization details intact.

Created "apiKey" variable in the environment.

Trying to run "getOrganizations" and it fails with the error.

 

I've checked the info here:

https://developer.cisco.com/meraki/api-v1/authorization/#authorization

https://developer.cisco.com/meraki/build/meraki-postman-collection-getting-started/collection-settin...

 

Could anybody reveal the screenshot of the working postman Authorization please.

 

Kind regards,

Ritor

 

5 Replies 5
Ryan_Miles
Meraki Employee
Meraki Employee

Screenshot 2024-06-24 at 19.56.12.png

 

Screenshot 2024-06-24 at 19.56.36.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.
Ritor
Conversationalist

Thank you.

Did the same - still error 401.

API key definitely correct.

No headers except default in the collection API call.

 

PhilipDAth
Kind of a big deal
Kind of a big deal

Any chance when you copy and pasted the API key there is a leading or trailing space, or the first or last character dropped?

PhilipDAth
Kind of a big deal
Kind of a big deal

Have you definitely got the correct organization/network name for whatever you are testing?  They are case-sensitive.

Ritor
Conversationalist

Found it.

Bloody web proxy. I forgot it is using auth before sending traffic to the internet.

Should've looked closely to the server reply first.

Get notified when there are additional replies to this discussion.