Skip to main content
The request template library is where all your reusable request definitions live. It’s a shared resource across your workspace — any journey can pull from it, which means a well-maintained library pays dividends every time you build a new workflow.

​
When to use it

Browse the library when you’re adding a request step to a journey and want to use an existing definition rather than starting from scratch. Manage the library when you’re onboarding a new API surface, importing from an OpenAPI spec, or cleaning up outdated templates.

​
Key concepts

  • Templates are shared — a template in the library can be referenced by any number of journeys and steps. Updating the template propagates to all referencing steps automatically.
  • Templates are not copied into journeys — steps hold a reference to the template, not an embedded snapshot. The live template is what runs.
  • Templates are versioned separately from journeys — changes to a template are reflected in steps that use it. If you need to lock a step to a specific template shape, consider journey overlays.

​
How it works

The library organizes templates by service or tag so you can find the right endpoint quickly. Each entry shows the template name, HTTP method, and URL pattern at a glance. From the library you can:
  • Browse and search by name, method, tag, or service.
  • Create a new template manually or import from an OpenAPI spec.
  • Edit the template’s request shape, declared values, and assertions.
  • View usage — which journeys and steps reference this template.
  • Archive templates that are no longer active without deleting them from history.
When you add a request step inside a journey’s Build mode, you pick a template from the library. The step then lets you configure how each of the template’s declared values is sourced for that specific journey.

​
Examples

Finding a template by service Use the search bar or filter by service tag (e.g., payments, identity) to narrow the list. The method badge (GET, POST, PATCH, etc.) and URL pattern help confirm you have the right endpoint before selecting. Viewing template usage Open a template and check the Usage tab to see every step that references it. This is helpful before making a breaking change — if twenty steps use this template, you’ll want to coordinate the update carefully. Keeping the library tidy Archive templates for deprecated endpoints rather than deleting them outright. Archived templates don’t appear in the picker when adding new steps, but existing steps that already reference them continue to work.

HTTP request templates

The full shape of an HTTP request template.

Import from OpenAPI

Generate templates automatically from an OpenAPI spec.

Request steps

How steps reference library templates inside a journey.

Template values

How templates declare the values they need.