/runs endpoints expose Armature’s workflow run history. Use them to pipe run results into BI tools, gate deploys on workflow status from CI, or build custom dashboards on top of the same evidence the Armature UI uses.
All paths are relative to the REST API base URL. All requests require an API key. Run data is redacted using the same policy as the dashboard and MCP API.
Search runs
| Parameter | Description |
|---|---|
range | Time range — 24h, 7d, or 30d. Defaults to 24h. |
workflowId | Filter to one workflow. |
status | Filter by run status — for example pass, fail, running. |
classification | Filter by evaluation classification. |
search | Free-text search across run metadata. |
page, pageSize | Pagination controls. |
sort | Sort key. |
Get a single run
Get the run trace
Get the run evaluation
List run tool calls
Typical polling loop
After dispatching a workflow withPOST /workflows/{id}/runs, poll the run until it reaches a terminal state, then fetch the evaluation:
Related
- Workflow runs in the dashboard — UI view of the same data.
- Dispatch a workflow — kick off the runs you then inspect here.