How to export multiple RequestBody types to the same endpoint in API documentation?

Get Support
1

Hello!

I have a question and would like to know if you can assist me. Recently, we started migrating from Postman to APIDog. However, many of our clients still use Postman, and when they export our documentation from the online page in OpenAPI or Swagger formats, they don’t find all of our routes.

We have routes with the same endpoint but with different body types and parameters (form-data and JSON). Please see the attached images. I’ve tried configuring the unique identifier for the endpoint using OperationId and Body Parameter (Content-Type), but when the collection is exported, only the endpoints with the requestBody in JSON are shown.

Is there another way to configure it so that all types of requestBody for the same endpoint are exported correctly?

Thank you in advance!
Apidog_VPo8nobx0Y.png
Apidog_G0HgjJHu5n.png

Apidog_4a152Mvr28.png
Apidog_4a152Mvr28.png1532×108 19.4 KB

notepad_62oXEldxsm.png
notepad_62oXEldxsm.png795×365 14.3 KB

2

Thanks for the feedback, according to the OpenAPI specification, the same path is considered the same endpoint. We will support exporting to Postman Collection format in the future to enhance collaboration with Postman.

3

Thanks!