Spec-backed templates
Generate candidates from OpenAPI, keep source-controlled fields synced, and review drift before it reaches downstream tests or journeys.
Request templates
Turn every API operation into a reusable, governed request.
Reqflo request templates give teams one canonical definition for how an API call is shaped, authenticated, asserted, versioned, and reused across tests, support runbooks, mocks, and journeys.
Account Origination API
Video hero slot
Retrieve an account application/applications/{application-id}GET
Create an account application/applicationsPOST
AuthReusable OAuth component pinned to rev 2Pinned
SyncSpec changed: review body and response shapeDrift
Reusable building blocks
Attach shared auth components, headers, assertions, scripts, and policies without copying fragile values into every request.
Versioned API behavior
Save named versions, pin dependencies, compare source updates, and keep historical context when a request changes.
Workflow
A repeatable path from source material to operational evidence.
- 01
Capture the operation
Import OpenAPI files from GitHub or create templates manually when the contract is not available yet.
- 02
Review the request shape
Confirm path params, query params, headers, body, auth, response expectations, and generated examples.
- 03
Compose shared behavior
Attach reusable components for auth, assertions, redaction, and scripts so updates can flow everywhere they are referenced.
- 04
Reuse with confidence
Use the same template in journeys, mocks, support flows, and release evidence without rebuilding it in every tool.
Why it matters
One source of truth for every request your team depends on.
Request templates are the shared API contract between product requirements, runnable workflows, generated evidence, and human review.
- See which templates are synced, detached, or drifted from source.
- Keep secrets as declarations instead of raw tokens.
- Pin or follow reusable auth components per template.
- Preserve older behavior as versions instead of losing manual context.
API governance
Platform teams standardize auth, headers, and environment variables across service owners.
Test creation
QA turns generated request templates into deterministic journeys without rebuilding calls in a test runner.
Operational runbooks
Support and success teams run approved operations from the same request definitions engineering trusts.
Start with your most repeated API workflow.
Bring your OpenAPI specs, manual API knowledge, and reusable auth patterns into one request library.