Unable to Get Access token to Orchestrator using API from Postman

[codemonkee (Tim)]

For explicate features of Postman, I’d recommend setting the Authorization Type to OAuth 2.0 on the Collection/Folder and then have any subsequent requests within the collection inherit from the parent.

Its a bit cleaner and nicer to work with then say writing Post/Test Scripts so that the Authorization Request is run before other requests when needed or running the collection.

Failed to get authenicated via the Orchestrator API

@Kakooza-Allan-Klaus - Based on the limited information, I would be interested in what you have configured in the Authorization Tab, as you should not be setting anything there for the initial authentication. In the method you have approached it, it is as simple as [image] I would also verify in the External Applications section of the Cloud Portal that you have copied your Client ID, Secret, and Scope details appropriately. You could then take it the next step and using the Tests tab, capt…

Another approach is to write a Pre-Script that mixes the use of Authorization on the Collection/Request that handles both the initial token and refresh tokens when the token has expired, or if you want to explicitly run an Authorization Request before another Request.