The below image is the documentation for my endpoint. I can't get this to work.
When I configure this in the portal I get back a 415 error.
Any general guidelines on how to configure this?
Update 2024-07-22
The regular way:
I’ve been doing some additional testing. Here's a more detailed description of my findings/problems.
The API wants to receive a JSON body like so:
{
"grant_type": "authorization_code",
"code": "abc***123"
}I tried to add fill out the portal like this:
This doesn't work and returns the 415 error.
What should I fill out in stead?
My cicumvention (doesn't suffice).
I configure one endpoint (access_token) to be a POST request (the request that will give back my bearer token). I then configure a second endpoint (Products) and use a dynamic value based on access_token and use it in the header Authorization. See images below.
This method does “work” but is not sufficient. The Products endpoint returns exactly the data it should, but this is as “deep” as I can go.
The reason this is not sufficient is that I need another endpoint that should dynamically use values from the Products endpoint. The limitation here is that there can be only one dynamic values source. So I can't use both the values from Products and the bearer token returned by access_token. So here the workaround has reached its limits. This could be fixed by adding a feature that allows one to use multiple dynamic values sources.
