Organize complete API suites
Use API Projects, Groups, physical or referenced Collections, nested flows, and ordered Requests to model real service behavior.
03 / Validate
Build API tests your team can rerun and explain
Model complete API flows, chain runtime data, verify responses, and retain request, configuration, and HTTP evidence within the limits your organization sets.
API Testing is a complete Armoury workspace, not a one-off request panel.
4 scopesfor typed variables
Replayhistorical executions
Traceretained HTTP evidence
Stateful API validation
Model the whole exchange, not just the endpoint.
Keep request definitions, runtime state, assertions, configuration history, and retained HTTP evidence together so a result can be rerun and explained.
Carry state through the flow
Resolve typed variables at project, environment, collection, and request scope, then use extractors and Save Variable assertions to chain calls.
Test more than the status code
Configure authentication, request bodies, transport options, HMAC, Hash, Timestamp modules, delays, repeats, conditional skips, and response assertions.
Explain why a run changed
Inspect retained Request and Collection reports, configuration versions, HTTP evidence, and replay lineage, then compare or apply selected historical configuration.
From request chain to evidence
Carry data from the first request to the final assertion.
Build the sequence, resolve runtime values at the right scope, execute it in order, and investigate the saved report when behavior changes.
Model the flow
Create an API Project, organize Groups and nested Collections, and define the Requests in execution order.
Add state and checks
Choose an Environment, resolve variables, generate runtime values, and validate status, timing, body, headers, cookies, or JSONPath.
Run and investigate
Send one Request or execute a Collection, then inspect reports, HTTP exchanges, versions, and replay history.
Backend behavior you can explain
Make backend behavior repeatable and reviewable
The saved definition, runtime inputs, ordered flow, assertions, and retained request and response evidence stay close enough to investigate a pass or failure. Coverage follows configured retention, redaction, and response-size limits.
Review plans and evaluation