One versioned source of truth for every request your team runs — tested in CI, debugged in production, and trusted by your agents.
payments /charges
14 templates/charges
Create charge
Decline → retry charge
8 steps · 1.4s · staging
The problem
They live in request collections, test scripts, QA docs, support runbooks, mocks, CI jobs, issue comments, and people's heads. Six tools, three workspaces, no source of truth.
Versioned templates that import from the spec your service actually ships.
Acceptance criteria mapped to executable journeys, with coverage written back to the tracker.
Runbooks declare intent, inputs, safety class, and approved templates — for humans and agents.
Mocks generated from real endpoints and templates, not hand-maintained copies.
Composable environment YAML resolved at runtime, captured with every run.
One coverage dashboard. Failing, stale, unmapped — visible before merge, not after.
01 / Coverage
Sync requirements from Jira, Linear, GitHub Issues, or Azure DevOps. Map acceptance criteria to the journeys, checks, and runbooks that validate them. Write summaries back to the tracker so product and engineering see the same number.
REQ-2418 / Idempotent retries
JiraCovered
11/13
Failing
1
Unmapped
2
Stale
0
AC-01
Duplicate POST returns original charge id
AC-04
Idempotency key required for mutating calls
AC-07
Concurrent retries collapse to a single side effect
AC-09
Key TTL is honored at 24h
AC-12
Replay after key expiry creates a new charge
Debug run / charge.retry
env: staging / branch: idempotency-spike / 1.4s
02 / Debug
Debug mode captures the scenario, inputs, environment, variables, requests, responses, timings, assertions, scripts, and AI step outputs. Failures stop being screenshots in Slack and start being evidence.
03 / Runbooks for humans and agents
Reqflo runbooks declare intent, required inputs, preconditions, safety boundaries, expected outputs, and the request templates that execute them.
support / mutating / requires approval
04 / Composable runtime
Config and mocks are where workflow tools lose teams. Reqflo keeps both source-controlled and composable, so your test environment is your real environment.
Environments
Import shared modules, overlay branch variants, and keep config in the repo where reviews already happen.
name: staging.payments
extends:
- ../shared/base.yml
- ../shared/observability.yml
overlays:
- when: scenario.retries
load: ./retries.overlay.yml
vars:
base_url: "https://staging.api.acme.dev"
api_key: !secret vault://payments/staging#api_keyMocks
Turn endpoints and templates into mocks for local dev, demos, QA, and third-party dependency testing.
/v1/charges
200 / seeded from charges.golden.json
/v1/charges
402 / scenario: card_declined
/v1/charges/{id}
200 / resolved from db.connector
/v1/balance
200 / static fixture
05 / Built into execution
Reqflo classifies workflows by safety, resolves secrets at runtime, and writes every execution to an audit trail. Sharing a journey does not share what runs it.
Secrets stay secret. Values are resolved by the runner and never returned by the UI.
Workflows declare their safety class. Mutating runs and production targets gate behind explicit roles and approvals.
See who launched each cloud run, what context it used, and which protected resources were involved.
Emit pass/fail results, assertion failures, environment readiness, and release validation status — not just raw API latency.
Reqflo is in private preview with engineering, platform, QA, and support teams shipping API-heavy products.