We have been using Postman for a while and we would like to have examples of the Request and the posibility to create a Folder for each environment instead having the examples Named: DEV_Whatever or STG_Whatever.
We would like to group the DEV or STG examples to go more quickly when doing a request, the request could be different for DEV and Staging because the ClientIds change or some data about the request.
The reason why we want them is that in Post/Put/Patch request(In the request that have a body basically), the body could be very different between environments
I don’t understand what you’re trying to explain. Could you share a bit more about your current structure, and what structure you desire and how the current Postman features doesn’t support that?
As you could see in the Image there could be elements like the senderId or the ReceiverId that in order to be faster in our test what we do is to create a example and save it under the endpoint.
There could be more fields that are enviroment specific, and we do not like the variables approach since it could led to a nightmare so what we miss is the ability to have folders of Examples and pick the example you want.
We could have two folders DEV and STG and leave there the examples so we do not have to navigate under a lot of examples and just navigate under the enviroment specific examples.
Hi @jgarcian. Postman Collections currently support folders. If you click the ellipsis button to the right od the name of a collection, you will see an option to add a folder. Do you mean you want to organize saved responses in a folder?
.