Getting an access token from OAUTH2

Im trying to access an API that contains training information on individuals in my company - the API is using OAuth2 to issue a token but I cant get it to do that! The developer that Im working with, has Postman installed on his machine and can request and get a token without issue but I get the following error:

{"status":"401","timeStamp":"2020-10-28T15:39:25+0000","error":{"errorId":"5b4095aa-e582-43ac-86a1-8508a3e9520c","message":null,"code":"invalid_client","description":"invalid_client","details":null}}

I have the Download tool setup as follows (I have put asterisks in place of the actual ClientID and Secret :

I dont see what Im doing wrong, or different from Postman!

API

Accepted answers

BrandonB

The API might require you to do something with the token like base64 encoding it or adding Bearer in front of it. It might also be called something other than Authorization depending on what they specify. This ultimately comes down to how the vendor has implemented their API. Take a look at this link that I just found: https://anymule.com/watch-out-for-base64-encoded-api-secret-keys.html

Have you tried the subsequent request in Postman yet?

All comments

BrandonB

In Postman, can the developer click the "code" button under the save button and show you the curl code? This is the easiest way to see if you are missing something.

Also, Oauth calls tend to be a GET request, but I may be wrong there.

craigja

Changing to GET returns this:

<cornerstoneApi>
<status>405</status>
<timeStamp>2020-10-28T16:13:44+0000</timeStamp>
<error>
<errorId>6c519deb-4e9a-4dc7-9fab-84c29122b4a8</errorId>
<message>Method not allowed</message>
<code>405</code>
<description>Method not allowed. Please see the service help page for constructing valid requests to the service.</description>
</error>
</cornerstoneApi>

JORGE4900

I was having the same issue. Postman would get the Oauth2 token very simply by selecting the configuration option from the dropdown menu. When passing the client id and secret via input tool, it worked. Works great now.

apathetichell

@alt_tush - @BrandonB would be the one to ask - but I'd strongly recommend posting some information on your errors. API's aren't the kind of thing were you have a lift and shift workflow and suddenly everything is awesome. This is usually because:

1) Security. Tokens/ClientIDs/ClientSecrets are specific to individuals and if I'm building a workflow that works for me - it will not work for you unless I compromise my credentials (and vice versa).

2) Wildly different APIs - without knowing what you are building an API for (ie what the API schema is) it can be totally off.

BrandonB

@alt_tush, this is a two download tool process. The first download tool has to call an authentication endpoint and pass the client ID, secret, etc. You put this endpoint in a Text input tool and then follow it with a Download tool where you enter the appropriate headers/payload.

Please take a look at this link for some images of workflow examples and a walk through of working with APIs: https://community.alteryx.com/t5/Engine-Works/APIs-for-Beginners-Integrate-All-the-Systems/ba-p/807437

alt_tush

Hell oapathetichell,

Yes, you are right. It is not simply lift and shift the workfow. But I just want to understand the steps if i want to implement the API connectivity using Alteryx what all steps or parameters are required.

Thank you for your response

bny_abo

Does anyone have a curl command version of getting the authorization token specifying the API Key and Secret?

apathetichell

Use postman and toggle to show code.

Quick Links

This months top contributors

mceleavey 383

mbarone 337

Hollingsworth 335

LanisC 335

JeffF 335