Feedback

Make sure that a duplicate API route does not automatically appear at the bottom of the list. Manually reordering routes can be tedious.

During daily usage, I suggest that Apidog add support for automatic theme switching based on the OS color scheme (light/dark mode). This enhancement would significantly improve visual comfort and reduce eye strain for users, especially during prolonged use.

Auto‑Fetch Token If Missing or Expired Currently, if no access token is present (or it's expired), ApiDog requires manual click on “Get Token”. It would be much smoother if ApiDog could: Detect absence or expiry of an access token before sending a request. Automatically initiate the OAuth2 flow (e.g., client_credentials or password grant) to fetch a new token. Attach the new token to the current request without user intervention.

You can currently see the historical changes to an endpoint, but it is more of an ‘audit log’ rather than something which is presentable to end users. API version control in Apidog is great, but it lacks the ability to view the changes between versions. Maybe a version can have an auto-generated doc or section where it lists all the changes made between versions. This would greatly reduce the amount of time spent writing out the changelogs manually.

When I change the request body examples, it overwrites the value of the previous example.

While setting up a new scheduled import in a project, it would be great if we could add custom headers. Sometimes, Swagger needs specific header to reach the json file, like the "Referer" header.

We are paid customer, but we feel the branch management has so many bug.Today when we try to do the merge, the merge filter function is broken again. The branch function is so important to us. Can you make this function stable? One of the reason we want to use API dog is because many people can manage the document together, but if the branch function is not stable, it will loose the reason we use API dog. Please check it. Thanks

We are paid customer, but we feel the branch management has so many bug.Today when we try to do the merge, the merge filter function is broken again. The branch function is so important to us. Can you make this function stable? One of the reason we want to use API dog is because many people can manage the document together, but if the branch function is not stable, it will loose the reason we use API dog. Please check it. Thanks

We use gRPC service for all of our applications. All the devs and QA wish that you have a bit automation capability for gRPC services. No pre-post scripts plus not able to create a folder with individual services and run the folder is disappointing. If you can implement these, I guarantee you that more than hundreds of our engineer and qas would be very happy!

Hello, it would be great if we could either define default headers (like component->responses) that would apply to all future APIs created OR have headers at root/folder level that would apply to all APIs inslide (and would be included in the documentation as well). Thanks for your consideration!