Feedback

Hi everyone, As far as I’m aware, Azure Key Vault integration is currently configured at the project level. This requires users to manually switch Key Vaults when changing between environments (e.g. Development, Test, Acceptance, and Production) and then separately open the provider settings to select the appropriate vault. It would be very useful to allow a Key Vault to be linked directly to a Project Environment. When a user switches environments, Apidog would automatically use the corresponding Key Vault and secrets for that environment. Alternatively, Apidog could support vault-specific references within variables. For example, the current syntax {{vault:foo}} could be extended to {{vault:my-production-vault:foo}} or {{vault:my-dev-vault:foo}}. This would allow users to explicitly reference a secret from a specific Key Vault without relying on a globally selected vault. Thank you for your time

Hi Apidog team, I’d like to propose a few features that are already available in tools like Postman and have proven to be extremely useful in day-to-day workflows. Bringing similar capabilities into Apidog could greatly enhance usability and productivity. Environment Variables Hover Preview When using environment variables in URLs (e.g., {{VARIABLE}}), it would be extremely helpful to display the resolved value when hovering over them. This would make debugging and readability much easier. Session Persistence (Open Tabs) It would be great if the application could remember all open tabs after a restart. Currently, losing the open requests interrupts the workflow, especially when working with multiple endpoints. Grouping Requests into Sessions / Tab Sets I’d like to have the ability to organize open requests into separate groups or “sessions,” similar to tab groups. This would help in managing sequences of requests by use case or workflow, improving clarity and productivity. Easier Access to cURL Representation Accessing the generated cURL command could be more immediate—ideally always visible or quickly reachable, for example in the right sidebar. This would speed up copying and sharing requests. General UX Alignment with Postman As many users come from Postman, aligning some UX patterns—especially around navigation, tab management, and request organization—could ease adoption and improve the overall experience. Thanks for considering these suggestions—looking forward to future improvements! Best regards, Debora

Hi Apidog Team, Please consider adding support in the module-level “Bind data source” option to use an existing Apidog request from the same module as the data source. Currently, data sources can be OpenAPI URLs, or Git-based YAML/JSON sources. It would be very useful if Apidog could simply run an existing request and use its response as the import source. Suggested flow: Bind data source → Existing Apidog request → Select request → Choose output type: OpenAPI / Postman Collection / other supported format This would allow users to handle custom authentication, headers, scripts, and external API calls inside a normal Apidog request, while still using Apidog’s existing import/sync logic. For example, a request could fetch a Postman collection from the Postman API, and Apidog could treat that response as a Postman Collection source and refresh the module. This would make the current data source feature much more flexible.

When using test scenarios, it would be nice if the auth token could be autofilled between requests easily, and would not be cleared when updating from an api spec or test case

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.

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.

The last changelog was for 2.8.29. We are currently on 2.8.32. I am curious what are the newer changes.

I tried to setup a local LLM model for using AI features. The connection not able to works beceuase some code issue I guess. I tried different endpoints but everytime the response is the same. It is also not working, If I don't set an API key, so setup a dummy one. I checked with powershell, end the endpoint is working in LMstudio. Please investigate it. We have a PRO subspription. Thanks!

When a request has variable extractors configured (e.g. extract $.id → global variable), Apidog generates the following pattern in the test script: ```js ;(async () => { const value = JSONPath({ json: pm.response.json(), path: expression, wrap: false }); pm.globals.set(formattedName, value); })(); ``` This async IIFE is invoked without await , making it fire-and-forget. The runtime does not wait for the promise to resolve before advancing to the next request in the scenario. As a result, global variables are not yet set when the next request executes, causing it to run with undefined or stale values. This breaks any multi-step scenario where each step depends on variables extracted from the previous response. Additional Context: The issue affects all auto-generated extractors across an entire scenario - every single extractor block has this pattern. Global timeout settings have no effect on this issue

When I click on “Generate client code” it is not exporting the body and headers values to me. Version 2.8.28