It was mentioned in one of my previous messages in another channel, but is there a timeline set for socket.io support?
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!


any update on this? im currently assessing Apidog for my company. but no support for socket.io is such a turn down for me. can i get detailed estimate?
Our current focus is on enhancing the features of the HTTP protocol. Of course, Socket.io remains on our roadmap for the second half of the year.
A rough estimate is the second half of the year, and the specific time cannot be provided yet.
any update on this? im currently assessing Apidog for my company. but no support for socket.io is such a turn down for me. can i get detailed estimate?
