Feedback

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

It does not open in the last position you were working on, requests, environments, etc.

Having a way to publish change logs similar to https://apidog.canny.io/changelog with RSS and search or filters would be a really nice feature to have. It could be as simple as creating different markdown files inside a "changelog" folder and have it rendered in one page with the ability to filter by tags etc. An example: --- title: Changes to the orders endpoint slug: update-01-01-2026 tags: ["orders", "rest-api"] --- ## Changes to the orders endpoint Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. The mydocs.com/changelog would show them all rendered in a single page using the metadata in each markdown update. And mydocs.com/changelog/update-01-01-2026 would allow us to share a specific update. And mydocs.com/changelog/feed.rss for the changelog in RSS format.

It would be great to have a way to set a custom color for each environment so it is immediately obvious where you are. It could be something similar to what AWS has (a 4px colored top border) or a different accent color or anything that stands out.

Sometimes we work with specific datasets for an extended period during a test scenario. Currently, Apidog does not remember the previous selection and defaults to selecting all of them every time. It would be a great improvement if the app remembered and pre-selected only the most recently used datasets.

When closing an endpoint, the cursor in the file browser moves to another document, what would be better is that it doesn't move to another point in case I don't want that behavior. The option of whether or not to allow that behavior would be better.

Ability to change font size for request and response content

It would be great if you could change the font family you like, either on the UI or text for the json response.

I’ve noticed that if I have different authentication data in the test case, it gets ignored in test scenario run. The token is taken from the endpoint instead of the test case. However, when I run the same test case outside of the test scenario (debug it > send), the token is applied correctly.