Choose the 'Use Token' button to set this as the currently used token. Postman will then display your access token to be used for testing. The only work around that comes to mind is to use oAuth1 which you can find. Depending on your browser, you may receive an alert to redirect you back to the Postman app. At this time we dont have a way to verify more than one redirect URI to an API key. The prompt on the authorization page is dictated by the requested scopes in the previous step. Postman will make the request to WHOOPs Auth URL specified above. Postman will take you to the LinkedIn authorization page, where you may be prompted to log into LinkedIn. Client Authentication: Send client credentials in body.

Note the Callback URL should be with the 'Authorize using browser' box checked if you are using the Postman Desktop app On this pm.Ensure that the correct environment is selected and click 'Get new access token':

The redirect URI is the URI (URL) to which DocuSign will redirect the browser after authentication. Set the type to OAuth 2.0 and Add auth data to to Request Headers just like in the. Values for Client ID and Client Secret are required to get an access token in the next step.Įach collection in the LinkedIn Marketing Solutions workspace will have its OAuth 2.0 Authorization settings pre-populated with the correct URLs, environment variables, and scopes to be able to successfully run the requests within the Use Cases folder. You have defined a redirect URI for your integration key. After creating the collection, click on it and jump to the Authorization tab. Fill in the environment variables as necessary.

Get postman redirect uri