Feedback

I have a scenario with referenced endpoint test cases and the same one as a regular (endpoint) scenario. When I reference the scenario with endpoint cases from another project, authorization doesn’t work. With a regular scenario where I use standard endpoints, everything works fine. Please fix this.

There doesn't seem to be a way to set up custom headers for response components. In particular the content type only supports some built in values where as I want to add "application/vnd.api+json" as the "Content-Type" header. It would be great to have the ability to add custom headers to Response Components.

It seems like I suddenly stopped seeing assertion results in Other > Script , unlike how it works for HTTP Request > Post-process > Custom Script . Previously, this used to work for pm.test . Could you restore this functionality? Or perhaps add the ability to write assertions directly within Database Script ?

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.

Current Capability: ApiDog API Client currently supports defining global parameters for Headers, Cookies, Query, and Body, which greatly improves efficiency when working with repeated values across requests. Suggested Enhancement: It would be highly beneficial to extend this capability to Path Parameters as well. Use Case Example: In my project, all endpoints follow a common prefix pattern such as: /api/{tenantCode}/users Currently, to handle the {tenantCode} path variable, I must define an environment variable like {{TENANT}} and reference it manually in each request URL. While this workaround is functional, having a native way to set global path parameters would provide the following benefits: * Efficiency: Avoids repetitive manual entry or env var substitution for each path. * Time-Saving: Especially helpful in projects with many endpoints using the same path prefix.

Getting this error: Error: "authorization" metadata cannot have multiple values when using grpc endpoints. Seems to be happening when Secure gRPC is selected (gRPCs).

It would be nice to be able to choose the default opening mode for an endpoint. You could choose between "Endpoint", "Edit", "Run", "Mock".

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.