Customzing oauth field names

[Mads_Nielsen]

I am trying to connect my app to TikTok using oauth.

I run into the following problem:

The problem happens due to the fact, that TikTok uses a different name for the client_id. They call it client_key. See their documentation for authorization here: TikTok for Developers and their documentation for access tokens here: TikTok for Developers

I was able to make the authorization part work, by appending the client_key as a parameter (see below)

Without doing the same for getting the access token, I get the error seen in the first screenshot.

If I try to append the client_key as a query param to the access token endpoint, I am never getting redirected, and I am just stuck on the tiktok authorization page.

I really wish that there was a way to customize - in the resource editor - what the keys are going to be named in the request, in addition to specifying the values. Hope it makes sense.

[Darren]

Hey @Mads_Nielsen! You're not alone, if it's any consolation. This request - or some variation of it - is something I've seen pop up a few times in recent weeks. The good news is that it's on our radar. I'll pass on your feedback and will hopefully have an update for you before too long.

In the meantime, there's a relatively simple workaround. You can set up a custom authentication flow on the resource, instead, and tweak it to meet the exact needs of whatever API you're working with.

Out of curiosity, are there any console errors when you get stuck on the authorization page after adding the client_key to the query params of the token endpoint? It seems odd that it wouldn't redirect you.