Recursive, or nested, variables only work while the environment is active.The Sleep Foundation editorial team is dedicated to providing content that meets the highest standards for accuracy and objectivity. Note: Environment variables can also contain Template Tags. Use variables within environment variable json configuration to reference other variables and minimize hard-coded values. This is especially useful for composing more complex variables such as the domain name in the following example. Recursive VariablesĮnvironments can reference other variables, including variables defined within itself. Here is the priority of environment, ranging from highest to lowest:įor example, if a variable is defined in a base environment and in a sub environment, the value in the sub environment will overwrite the one in the base environment. If two variables with the same name are defined in multiple environments, the environment with higher priority will win. These will also override any variables defined within a sub environment or base environment.

Any variables defined at the folder-level will be available to all requests within that folder. You can access a folder’s environment from the folder dropdown in the sidebar. Folder Environmentsįolder environments are a rarely used feature, but can be invaluable for specific use cases. Note: Sub environments can be created as Private, meaning they will never be synced or exported. Once sub environments exist, they can be activated via the environment dropdown. They are also sometimes used to defining variables for different users of a single app. Sub environments are most commonly used for store variables related to production, staging, or development services. A common use for the base environment is to store default variables that will not change across production, staging, or development services such as resource names, languages, sample data, etc.

Variables in the base environment are available throughout the entire workspace, even if other environments are defined. Base EnvironmentĪ base environment is assigned to every workspace within Insomnia and can be accessed via the environment manager. Note: Hovering over the placeholder with your mouse will show the current value. Clicking on the button will show a modal dialog for further editing. Once a variable is selected, it will be displayed with a colored placeholder. Allow the autocomplete to show automatically as you typeĪfter you have set environment variables, you can access the variables via autocomplete dropdown menu.Summon the autocomplete dropdown by pressing Control+Space.Referencing Environment VariablesĮnvironment variables can be referenced in (almost) any text input within the Insomnia application.

Note: Variable names must only contain letters, numbers, and underscores. The Manage Environments modal allows you to access and edit your base and sub environments. From here, you can edit the base environment, create sub environments, assign colors, and more. Access the environment manager through the environment dropdown menu at the top of the sidebar. Environment BasicsĪn environment is a JSON object containing key-value pairs of the data you want to reference. Request using base URL and ID variables that can be reused. Common variables are base URLs, authentication tokens, and resource IDs. Set up environment variables to reuse values across multiple requests.

Define insomnia