Skip to main content

HTTP Requests

The http step type executes HTTP requests and captures the response for extraction and assertion.

Basic Syntax

The url can be a relative path (resolved against config.http.base_url) or an absolute URL.

Request Configuration

Base URL

Set a shared base URL in workflow config:

Methods

Replay supports standard HTTP methods:

Headers

Set global headers in config (applied to every request):
Override or add per-step:
Step headers take precedence over config headers.

Body

Send JSON bodies as a map:
Use template variables:
For raw JSON strings:

Response Structure

The HTTP runner returns a structured result:
  • status — HTTP status code
  • data — Parsed JSON response body (or raw string if not JSON)
  • header — Response headers

Extraction

Use JSONPath expressions to extract values from the response:

Assertions

Assert on the response:

Debug Mode

Enable debug logging to see request/response details:
Or pass --debug on the CLI to enable debug for all workflows.

Example: Full Auth Flow

TLS

Replay accepts self-signed certificates in development environments. For production, ensure your servers use valid certificates.

What’s Next?