API with content type: application/x-www-form-urlencoded

Hi everybody,

I’m having an issue setting up an API Post request with the content type: application/x-www-form-urlencoded.

I’ve managed to get the API to work in Postman using the body format option for x-www-form-urlencoded. However, this isn’t an option in Bubble.

Furthermore, using Postman the API still runs correctly when the body type is set to Raw and the variables are separated by “&”, however, when copying and pasting the exact body from Postman, Bubble still fails.

Does anybody have any suggestions? I’ve gone round in circles so many times now.

So summarise, has anybody had success with the application/x-www-form-urlencoded format. If so, how’d you manage it?

Thank you

Thank you for your support @NigelG. Most of what that thread had gone over I’d attempted. Although from reading through, I noticed that the Authentication header displayed was before the Content-Type. I didn’t think this would have made any difference as it doesn’t in Postman. But lo and behold, I swapped them around and it worked like a charm!

Thanks for your support!

1 Like


The API connector is a little … fussy … at times :slight_smile:

1 Like