Feedback

Please add a new rapid third twitter api: twitterapi.io . It's very useful!

When I DO NOT specify the Auth at the root level, the generated openapi file contains an empty security object `` security: {} ` instead it should contain an empty array ` security: [] ``

Hey! I am moving over from postman, and work in the integration space of the world, so understanding API's is part of my life. Postman, for OAuth 2.0 has auto-refresh tokens, which is awesome, as when the token expires, postman will get a new one without me needing to go and click on to refresh/get. This would be super awesome, and make life super smooth compared to always going to refresh or get a new token depending on the service/timeout. Some services I work with have 30 minutes for the token.

I managed to reduce the size of the window 'frame' by using CTRL -, which has made it incrementally smaller, but I can't seem to make it bigger by using the usual CTRL +. I can see in settings there is a font size, but this only affect the main content of the app, not the window controls at the top. Unless I am missing something it seems like CTRL + is not coded to increase the size?

When I export the API documentation as json or yaml, the exported file has the following issues when viewed on Swagger editor: Some schema objects do not expand and collapse Example values are not visible Sample payload is not getting created using the example values of each param Despite renaming the existing tags, the older tag names are also getting exported in the json/yaml.

There have been many times where I wanted to filter the endpoints by request type (POST, GET, etc). Although the filtering is much better than Postman's, both are still missing the ability to filter by request type.

Our API allows 2 types of Authentication: Bearer and API Key. Unless we are missing something, we can only choose 1 type of authentication. The root folder should allow multiple auth types to be declared. Each endpoint should allow to select 1 or more of these auth types. (maybe a multiselect?) The generated docs should show what auth methods are available, and for each endpoint, which one(s) are accepted. At the moment, it is very annoying testing each endpoint using different auth methods, as we have to go to root folder, change auth types then run the endpoint again.

Hi! Thanks for very useful program! There is one feature that I really miss - the ability to search among endpoints by parameter name or by the name of a member of the returned structure or by part of the description

Is there a way to mark the request body as required or not? We have a Swagger comparison script that compares Apidog Swagger spec vs. TypeScript-based Swagger spec and it seems that "required" field in the Apidog Swagger spec is missing even though the request body is required for some of our API endpoints so the script is currently failing.