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:
10
Categories
- All Categories
- 2K Forums
- 1.8K Platform
- 159 Academy
- 324 Resources
- 1 Board Knowledge Base
- 50 Best Practices
- 49 How-To Guides
- 19 Board Advocacy Program
- 191 Blog
- 4 Groups Hub
- 4 About Groups
- New Community Members
- DACH
- Japan
- 4 Community Captains
- 1 About Community Captains
- 2 Meet the Community Captains
- 1 Topics & Thought Starters
- Learn from the Board Captains
- Release Notes
- Academy
- 2 Board Academy
- 8 ILT/VILT Course Catalogue
- 13 e-Learning Course Catalogue
- 4 Academy Forum
- 1.2K Idea Exchange
- 337 Partner Hub
- 94 Support
- 14 FAQ's
- Customer Support Portal
- 54 Support Articles
- BEAP