This topic was automatically generated from Slack. You can find the original thread here.
Raymond Camden : Query - perhaps dumb. If an API requires OAuth, I could just write a Node step that hits the endpoint to get an access token, and then uses the access token to hit the endpoint I care about. That should just work, but is there a better way? (Ie a “Pipedream” way)
Dylan Sather (Pipedream) : Do you have your own app with its own OAuth client ID / secret in this case, or are you just connecting to the API as a user, like you would for OneDrive or Twitter?
Dylan Sather (Pipedream) : What’s the API? We can create a custom “app” in Pipedream where you can enter your own client ID / secret and we’ll automatically generate access tokens for you like a normal OAuth Pipedream integration.
Raymond Camden : Ehh - I wouldn’t want you to build an app for this, I know I always say “Im just playing”, but this is really just me experimenting. But you did kind of answer my question. I could do as I said (fetch to get Access Token, then do the hit), ask yall to build one, or build my own app in the future. is that a fair summary?
Dylan Sather (Pipedream) : That’s exactly right. If you want us to build the app config it’s generally not too hard (takes us minutes) so we’re always happy to help
Raymond Camden : k - thx. as it stands, this particular idea i had hit a brick wall pretty quick. Battle.net used to support returning character info w/o requiring you to be a particular character owner. now you only get characters via a user login flow and only for that user.