Community Spring Cleaning week is here! Join your fellow Maveryx in digging through your old posts and marking comments on them as solved. Learn more here!

Alteryx Designer Desktop Discussions

Find answers, ask questions, and share expertise about Alteryx Designer Desktop and Intelligence Suite.
SOLVED

Uber API OAuth 2.0 bearer token

evdxn
5 - Atom

Hi All, 

 

I've been using Alteryx for a few years but am brand new to API connections. I'm currently attempting to incorporate Uber Business Receipt data into a reconciliation workflow but am struggling to get it configured using the Download tool. I did see in this article by @TashaA that some OAuth 2.0 methods do not work so well in Alteryx and am worried that's what I'm running into here. Thus far, I've passed the Authorization Endpoint URL from a Text Input tool to the Download tool, but have consistently ended with 302 Found. In the Download tool, I've tried to add the Client ID and Client Secret to the Payload tab, using the POST action as well as entering the credentials into the the Connection tab. Any light that can be shed on this would be of great help! Uber documentation can be found below for context

 

https://developer.uber.com/docs/businesses/guides/authentication

https://developer.uber.com/docs/riders/guides/authentication/user-access-token

https://developer.uber.com/docs/businesses/references/api/v1/business-trips-trip_id-receipt-get

 

Thank you!

5 REPLIES 5
josephschafer
Alteryx Alumni (Retired)

Hmm,

 

302 is generally considered to be a Server side issue, not necessarily a Client side issue.  From their documentation, it is meant to convey "Retry request on given redirect URI."  So the issue might not even be with your API request.

 

That said, do they respond additionally with a different endpoint (URI) to contact within the Download Data response?  Perhaps there's a different endpoint for that API call?

As an FYI, typically when a Bearer Token scenario is at play, I have to build one workflow retrieve the token via a first API call and then I'd pass the Bearer token into a child workflow (a macro) in order to use the latest Bearer Token value in subsequent calls for that session.

 

 

 

evdxn
5 - Atom

Was finally able to configure the Download tool to receive the Bearer Token and pass it downstream in the workflow (attached) to call the business receipt data. Some solid teamwork, this uber documentation, and this article were immensely helpful!

jayviz
7 - Meteor

Thank you, your workflow helped me to solve one of my API problems to pull data from PostgreSQL database.

ajrajeswaran
5 - Atom

Thanks - this is helpful.

Aju_6
5 - Atom

in this what should be at the place of grant type - client_credentials (can you plz provide an exmaple like what exactly we should have in this place)

Labels