Feature Suggestions & UX Improvements
Debora Fumo
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
franki
Regarding Easier Access to cURL Representation, Apidog already supports quick cURL copying. You can right-click the corresponding API in the left-side directory tree and select Copy cURL to quickly share the request or reproduce it in a terminal.
Regarding General UX Alignment with Postman, we understand that you’d like Apidog’s navigation, tab management, and request organization experience to be more aligned with Postman, helping reduce the learning curve when migrating from Postman.
To help us evaluate these UX improvements more accurately, could you please let us know which specific operations in Apidog feel inconvenient or differ significantly from your Postman workflow? For example, this could be related to navigation, tab management, request organization, entry points for common actions, or any specific workflow after migrating from Postman.
franki
Thank you for your detailed suggestions. We’ve reviewed and organized your feedback item by item.
Regarding Environment Variables Hover Preview, we have recorded this request and will submit it to our product team for evaluation. In addition, if the variable is used to represent a dynamic path parameter, such as a user ID or order ID, we recommend using path parameters instead, for example:/users/{userId}, You can then manage the value of userId in Params. This makes the API structure clearer and easier to manage and debug.
Regarding Session Persistence / Open Tabs, Apidog currently supports restoring previously opened tabs after the application restarts. To help us investigate further, could you please provide the following information?
1. Your Apidog version;
2. Your operating system and version;
3. The exact way you exited the application;
4. Whether all tabs failed to restore, or only some of them;
5. A screen recording of the issue, ideally showing the full process: opening multiple tabs → exiting the application → restarting the application → tabs not being restored.
Regarding Grouping Requests into Sessions / Tab Sets, we’d like to confirm whether your request is to group currently opened request tabs by business scenario or debugging task, such as “Login Flow,” “Order Flow,” or “Payment Debugging,” and quickly switch between these groups.
Currently, Apidog supports using Folder / Module to organize APIs structurally. If you need to execute multiple APIs in sequence, you can also use Automated Testing to arrange and debug the workflow.
If your need is more about managing currently opened tabs and saving or switching between different debugging contexts by task, please share more details about your specific use case. We’ll further evaluate this type of Tab Sets / Sessions capability.