Skip to main content
Request templates are the source of truth for HTTP request structure in Reqflo. They define what a request looks like — method, URL, headers, body — while journeys compose those templates into end-to-end workflows and own the sequencing, value wiring, and validation logic. Think of templates as the “what to send” and journeys as the “when, why, and with what data.”

​
When to use it

Templates matter most when you’re working across multiple journeys that call the same endpoints. Define the shape once in the template library, then reuse it in as many steps as you need. When an endpoint changes, you update one template instead of hunting through every journey that references it. If you’re defining a new API surface, consider importing templates from an OpenAPI spec rather than creating them by hand.

​
Key concepts

  • Request template — a named, reusable definition of an HTTP request: method, URL pattern, headers, body shape, and declared values.
  • Request template library — the central catalog where all templates live. Steps pull from this library when you add them to a journey.
  • Template values — declarations of what data a template needs (path params, query params, headers, body fields). Journeys decide how to supply those values.
  • Template assertions — assertions defined at the template level that apply whenever the template is used in a step.
  • Example and Faker values — default or generated values attached to a template for previewing requests and populating test data automatically.

​
How it works

When you add a request step to a journey, you select a template from the library. The step inherits the template’s request shape. You then configure how each declared value is sourced — from run inputs, variables, prior step outputs, hard-coded values, secrets, or environment values. The template stays separate from the journey: the journey holds a reference to the template, not a copy. If the template is updated, every step that uses it reflects the change.
Templates define structure and intent. Journeys own execution context. Keeping these separate means a single well-defined POST /payments template can power a happy-path journey, an error-case journey, and a support runbook — all without duplicating the request definition.

Request template library

Browse and manage the central catalog of reusable templates.

HTTP request templates

The full shape of an HTTP request template.

Template values

How templates declare the values they need.

Template assertions

Assertions defined at the template level.

Import from OpenAPI

Generate templates automatically from an OpenAPI spec.

Request steps

How steps pull from templates inside a journey.