Hey, I saw lots of blog post regarding Bubbles API & OAuth2 Custom Token, but after several attempts and reading lots of blogs, I still do not find the issue.
As you can see the request works with Curl and with Postman:
Doing the same in Bubbles API:
The result I am getting:
And just btw, the same happens if I do the authorisation as a separate call:
Creates the same result
I am really clueless, and appreciate hints what I am missing here
Your body parameters are not json. I guess you’d have to format them as json
No. The problem is not there.
I suggest to send the call to service like requestbin from both api connector and postman and compare each request. I think that your issue could be related to username and password url encoding.
Thx for the hint using requestbin, I was also thinking about that approach, but not yet found an easy to use tool. Actually, you are right, it is an encoding issue, in this case of special characters. Here the part of the payload shown by requestbin:
Postman:
resource=https%3A%2F%2Frollin.api.meine.bg-qseh.de
Bubble API:
resource=https://rollin.api.meine.bg-qseh.de
So, using the already encoded payload in Bubble its seems working. Question remains, is there a way to convince Bubble.io to perform the encoding itself?
