I do a few test and see very strange behavior of the API connector.
I think it’S a bug and must be reported to Bubble.
Test a) Put only a parameter with no header
Content type is to application/json (wrong, if we consider that json body is empty, this should be application/x-www-form-urlencoded)
Test b) Put paramter with application/x-www-form-urlencoded in header. Bubble overwrite it to json again.
Test C) Put a body json (no parameter) and add header application/x-www-form-urlencoded… Header received is… application/x-www-form-urlencoded (Wrong, should be json, because there’s a json body!)
Test d) But form data body type, parameters, and header to application/x-www-form-urlencoded … Header stay form data (and I think this is the right think)
@neerja Can you confirm this? if yes, maybe add a body type for application/x-www-form-urlencoded and use parameters like we expect it to work
Now, You may try this:
add parameters, set querystring
In json body, set only {}
I really don’t know if this will work, but the header will stay application/x-www-form-urlencoded