Environments

Test the same API against different deployment environments — Development, QA, Staging, Production, or custom setups — without manually changing the API configuration. Configure base URLs, switch environments with a click, and set a workspace-wide primary environment.

Environments allow you to test the same API against different deployment environments without changing the API configuration manually. For example, you can configure separate environments for Development, QA, Staging, and Production and switch between them with a single click.

Key capabilities

• Create and manage multiple environments.
• Configure a base URL for each environment.
• Keep environments isolated within each workspace.
• Quickly switch between environments.
• Use environments across Request Builder, Test Suite, and Request Chain.
• Set a Primary Environment for the workspace.
• Automatically use the selected primary environment across supported screens.

Creating an environment

Users can create multiple environments within a workspace. For each environment, configure the required Base URL — for example:

This allows the same API request to be executed against different environments without manually changing the API URL.

Workspace-level environment isolation

Environments are isolated within each workspace. This means each workspace can maintain its own environment configuration without affecting environments configured in other workspaces. This is useful when different workspaces represent different projects, teams, or API configurations.

Switch between environments

Users can switch the active environment with a single click. Once an environment is selected, the configured environment values are used when executing APIs from supported areas of the application. This makes it easy to test the same API across different environments without modifying the request itself.

Use environments across the application

Configured environments can be used across:

• Request Builder
• Test Suite
• Request Chain

This provides a consistent environment configuration across API development, testing, and workflow execution.

Primary environment

Users can designate one environment as the Primary Environment. Once a primary environment is configured, it is automatically selected by default across the supported screens.

Users can still switch to another environment when they need to test against a different deployment.

Example workflow

Create Environments
        ↓
Development | QA | Staging | Production
        ↓
Set QA as Primary Environment
        ↓
Request Builder
        ↓
Test Suite
        ↓
Request Chain
        ↓
Switch Environment When Required

Core value proposition