Skip to main content
hitspec is configured through a hitspec.yaml (or hitspec.yml) file in your project root. All settings are optional — hitspec uses sensible defaults when no config file is present.

Creating a Config File

Run hitspec init to generate a starter configuration:
This creates a hitspec.yaml and an example.http file.

Full Configuration Reference


Options Reference

General

Network

Headers

Headers defined in individual requests override config-level headers with the same name.

Output

Execution

Environments

Define per-environment variables inline:
Select the active environment with --env:
Variables defined in the active environment are available via {{variableName}} interpolation in your test files.

Stress Testing Profiles

Define reusable stress test profiles:
Use a profile with the --profile flag:

hitspec looks for config files in this order:
  1. Path specified by --config flag
  2. hitspec.yaml in the current directory
  3. hitspec.yml in the current directory
If no config file is found, all default values are used.

CLI Overrides

CLI flags always override config file values:
Last modified on June 16, 2026