Feedback

Hi ApiDog Team, I would like to request the addition of a Feedback Form feature within ApiDog's API documentation platform. This feature would allow API consumers to easily submit feedback directly from the documentation, providing insights into API usability, clarity, and potential issues. Key Features Requested: A simple, customizable feedback form embedded within the API documentation. (v1) Options to collect user feedback on API endpoints, documentation quality, and overall experience. (v1) Ability to categorize feedback (e.g., Bug Report, Suggestion, Question). (v1) Integration with third-party tools (e.g., Jira, Slack, GitHub Issues) for seamless feedback management. (v2) Analytics and reporting to track common feedback trends. (v3) This would significantly improve the developer experience and help API providers proactively address concerns. Thank you for considering this request! Best regards, Hristian

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.

When navigating from my site to the API documentation, the attached environment variable is lost. Specifically, when I click on the "Try Out" button within the documentation, the environment variable is not populated, resulting in no value being displayed in the environment section. This issue may hinder the functionality of testing API endpoints, as the expected environment variable values are not retained, impacting the overall user experience.

The text formatting of the single-line endpoint description is not working correctly. Special characters remain visible in the text. The multi-line description is displayed correctly.

We use Postgres databases with SSL enabled, as of right now there is no way in Apidog to specify SSL should be used to connect with the database, resulting in an error like below error: no pg_hba.conf entry for host "x.x.x.x", user "user", database "database", no encryption at Parser.parseErrorMessage (/home/runner/.npm/_npx/ae100d9c15b15973/node_modules/pg-protocol/dist/parser.js:283:98) at Parser.handlePacket (/home/runner/.npm/_npx/ae100d9c15b15973/node_modules/pg-protocol/dist/parser.js:122:29) at Parser.parse (/home/runner/.npm/_npx/ae100d9c15b15973/node_modules/pg-protocol/dist/parser.js:35:38) at Socket.<anonymous> (/home/runner/.npm/_npx/ae100d9c15b15973/node_modules/pg-protocol/dist/index.js:11:42) at Socket.emit (node:events:518:28) at addChunk (node:internal/streams/readable:559:12) at readableAddChunkPushByteMode (node:internal/streams/readable:510:3) at Readable.push (node:internal/streams/readable:390:5) at TCP.onStreamRead (node:internal/stream_base_commons:190:23) {

Hi, your product is amazing! Could you please add a search for methods that use a specified scheme (or component) in the request or response. This may be similar to using tags in the search filter. Currently we have to add special tags for each method, which is inconvenient when there are a large number of methods and schemes.

Please add funcionality to refer scenarios from other projects which have database connection in it

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: [] ``