Support x-www-form-urlencoded body type for POST API Calls

Andrea Duò
Employee




At the moment, in REST API Calls if I have to set up a POST request with a body, the body type can only be in json format, which means that the only value supported for header Content-Type is "application/json". In some cases, especially API endpoints that return tokens but they are not standard OAuth2 flows (like in some configurations of Netsuite APIs), the body needs to be in x-www-form-urlencoded, which means that the Content-Type header is "application/x-www-form-urlencoded". This enhancement would considerable expand the number of REST APIs we could connect to.
Tagged:
12