Currently, when using the “Try It Out” feature for endpoints that include a request body, Apidog displays all JSON fields pre-filled, requiring the user to manually delete the fields they do not intend to send.
This results in a less fluid experience and can create confusion, especially for non-technical users who may not understand why unwanted fields must be removed from the JSON before executing the request.
Since the documentation is often used by a wide range of profiles — developers, QA, business analysts, and even external partners — this behavior can become a usability barrier.
Suggested enhancement:
The “Try It Out” experience for endpoints with a request body should follow the same pattern used for query parameters, such as:
Displaying only the structure of the fields, without pre-filled values.
Allowing users to fill in only the fields they intend to send, leaving the rest empty.
This approach would make the process more intuitive, cleaner, and aligned with the core purpose of good API documentation: enabling anyone — technical or not — to test and understand the API’s behavior without risking errors or confusion when constructing the JSON.
Example in the attached readme.
