Feedback

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

Hello Apidog Support, We are importing our API definition from an OpenAPI 3.0.3 specification. We have several request header parameters where the schema is referenced via $ref. The referenced schema is a string enum, and it also contains the x-apidog-enum extension with names and descriptions. Example: parameters: - in: header name: x-custom-source required: true schema: $ref: '#/components/schemas/SourceSystemEnum' components: schemas: SourceSystemEnum: description: Source system identifier type: string enum: - system-a - system-b example: system-a x-apidog-enum: - value: system-a name: System A description: Example source system A - value: system-b name: System B description: Example source system B After importing the OpenAPI file, the schema itself is recognized correctly in Apidog: if we open the schema/model, the field is shown as an enum and the enum values are visible. However, when we open an endpoint and try to execute a request in the UI, the request header field is displayed as a simple text input. It does not appear as a dropdown with the possible enum values. Could you please confirm whether Apidog supports dropdown rendering for request header parameters when the enum schema is referenced via $ref and includes x-apidog-enum? If this is supported, could you let us know what the expected OpenAPI structure should be? Thank you.

I'm experiencing a persistent bug where GraphQL suggestions disappear after switching between tabs. The Problem: > Schema is "Fetched" successfully, but autocomplete (Ctrl+Space) stops working once I switch to another endpoint and come back. It only shows basic word suggestions (abc icons), not the actual GraphQL schema fields. What I've tried (and failed): Disabled "Optimize in-project tab rendering". Cleared %AppData% cache and local storage. Manual schema refresh. Re-installing the app. The only temporary fix is restarting the entire app, which is very frustrating for large collections. This happens on both Desktop and Web versions. Please fix the state management for GraphQL tabs.

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

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

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.