Hi, I’m using the HTTP Request node to contact to an API that requires a different refresh token URL.
Now going to connection and filling in the information I can specify only the access token url but not a different refresh token url. is it possible?
My second question is that this API requires a different naming for client id, it should be client_key=<client_id>
Is there a way to have both of these without me building the auth on my own?
Hi @Jon, thank you so much for the quick response.
I couldn’t exactly find information in the RFC of the OAuth2 Implementation about whether refresh token URL should be the same as access token.
But sadly the service still uses a different path, I still didn’t test yet whether this will represent a problem since I’m not that far to get it authenticated.
Still unfortuantely throughout my OAuth2 journey i noticed many APIs doing wonky implementations.
It’s definitely OAuth2, no key parameters or unique identifier.
I have been looking at a few implementations of the TikTok API and it doesn’t look like any of them use the refresh url which is interesting, What happens if you just try to connect using the fields we offer up?