improvement(api): add native support for form-urlencoded inputs into API block #1033
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
add native support for form-urlencoded inputs into API block
Type of Change
Testing
Tested the same request here & in postman, ensured that the responses were identical
Checklist
Screenshots:
Before (even adding content-type to application/x-www-form-urlencoded it still used application/json):

After (respects the users content-type, converts json body into url encoded entry):
