Skip to main content
An Environment is a named configuration of system-level values for a target system: base URLs, service-specific settings, and environment-specific values like feature flags or rate-limit overrides. When you run a journey, you pick an environment to tell Reqflo where to send the traffic.

​
When to use it

You use environments any time a journey can run against more than one deployment of a system — which is almost always. Typical environments:
  • sandbox — isolated testing against synthetic data.
  • staging — pre-production system, real infrastructure, not real users.
  • production — live system; use with care.
You can also create team-specific or feature-branch environments if your infrastructure supports it.

​
Key concepts

Environments describe the system target; cases describe the run data. This is the most important distinction. An environment answers “where does this traffic go and what service config applies?” A case answers “what values does this run use?” You combine them: the “Expired token” case against the staging environment is a valid, complete configuration. Environment values are pulled in at run time. When you select an environment before running, Reqflo resolves the environment’s values and makes them available to steps. Steps configured to use environment values (like base_url) get the right value automatically — no manual override needed. Environments are managed by admins. The actual environment definitions — which services, what URLs, what config — live in admin settings. Journey authors select from available environments; they don’t define them. See Service environments. Environment values combine with cases and run inputs. All three layers work together: environment supplies the system config, a case supplies the test data, and any remaining gaps are filled by run inputs or the journey’s own variable definitions. Sandbox mode lets you temporarily override any values for experimentation without saving a formal case. It’s useful for one-off testing but isn’t meant for reusable configurations — save those as cases instead.

​
How it works

  1. An admin configures environments in Admin > Service environments.
  2. When you run a journey, you select an environment from the available list.
  3. Reqflo resolves environment values (base URLs, service config) and injects them into the run alongside any case values and run inputs.
  4. Steps that reference environment values receive the correct value for the selected environment automatically.
From the CLI: 
reqflo run checkout-flow --env staging --case "Happy path"

​
Examples

The same journey run against two environments:
Environmentbase_urlfeature_flag_new_checkout
sandboxhttps://sandbox.api.example.comtrue
productionhttps://api.example.comfalse
The journey definition doesn’t change. The environment provides the right values for each target automatically.