Allow params / variables to be scoped per request
Feature Request
I would like to be able to use params or variables scoped to a single request. Maybe this is already possible, but I can’t seem to work it out.
I like to use request variables as I find it easier to quickly change a variable, rather than directly changing the json body. A use case might be that I have a resource-id defined in a environment, and defined as a request variable (can be enabled / disabled). In this case, priority should be 1 - request variable, 2 - environment.
A work around is using environments, but i often have use cases where it wouldn’t make sense to define all my variables in a environment as it would get long and unwieldy.
See this implementation in hopscotch as an example.
Linuxv2025.4.0
This is definitely something I want to add. Thanks for the request!
Used other tools that had the global/works env management just like yaak, excellent, but also has the ability to define request variables. In one tool these request vars after being defined appeared in the request description as text edit fields, which was nice, because when you came back later and opened the request you could just copy/paste or type, for example an item id, right into the text edit field instead of searching for the spot in the json and then trying to put the value in between the quotes in the json field. The request vars could also be used in the headers and param too.
Yes, RapidAPI (Paw) comes to mind here. I’m planning to do something very similar. Love the idea of being able to edit a bunch of values in a single place.
Hoping to take a crack at this shortly. I’d like to implement something that solves both:
- Ability to override environment variable on the request level
- Define request-specific “placeholder variables” that will be fillable from a central location within the request