Skip to main content
Environments in Reqflo describe the system target for a journey run — which services to talk to, at which base URLs, with which environment-level configuration. Service environments are configured at the workspace admin level so they can be shared across every journey that calls the same services.

​
When to use it

Configure service environments when:
  • Your workspace has multiple deployment targets (sandbox, staging, production) with different base URLs.
  • A service has environment-specific configuration values that every journey calling that service needs.
  • You want to let engineers switch a journey between environments at run time without editing the journey definition.

​
Key concepts

Environments vs. cases. This distinction matters: an Environment describes where a journey runs (the system target — services, URLs, infrastructure config). A Case describes what data the journey uses (test inputs, value presets, saved scenarios). They are separate and can be combined: you can run Case “Happy path” against the “Staging” environment without any conflict. Per-service configuration. Each environment entry is scoped to a service. A service entry can hold:
  • Base URL — the root URL the service’s request templates resolve against in that environment.
  • Service-level config values — any additional environment-specific values the service needs (API versions, feature flags, region settings, etc.).
Value resolution. When a journey runs with an environment selected, environment values are injected into the value resolution chain. Step-level and journey-level values take precedence where there’s a conflict. See Concepts: environments for the full resolution order.

​
How it works

1

Open Admin → Service environments

You’ll see a list of services registered in the workspace, each with one or more environment entries.
2

Add or edit an environment entry

Select a service, choose the environment name (e.g., staging, production), and set its base URL and any additional config values.
3

Select the environment at run time

When running a journey in the editor or via CLI, pick the environment to use. The journey pulls base URLs and service config from the matching environment entry.

​
Examples

Three environments for a payments service.
EnvironmentBase URL
sandboxhttps://sandbox.payments.example.com
staginghttps://staging.payments.example.com
productionhttps://payments.example.com
Each entry can also carry service-level config values — for example, a timeout_ms or api_version that differs between environments. Running locally against sandbox. 
reqflo run checkout-flow --env sandbox
Running in CI against staging. 
reqflo run checkout-flow --env staging --reporter junit --output results/