Set up the workflow
Create a run with POST /api/projects/:id/runs, execute it with POST /api/runs/:id/execute, and inspect it with GET /api/runs/:id. Request bodies depend on the selected case and execution configuration; use the connected MCP tool schema or your deployment’s API contract rather than guessing fields.
Run lifecycle
POST /api/projects/:id/runsCreate a run from the selected cases and configuration.POST /api/runs/:id/executeRequest execution. Network and concurrency gates still apply.GET /api/runs/:idRead the run and wait for a terminal result in your CI logic.Handle non-2xx responses explicitly. Never treat a queued request, timeout, or missing result as success. Keep CI tokens out of client-side code.
Before using this in a release gate
Validate one representative journey in the intended environment, review its outcome, and agree who owns failures. Use the current deployment’s configuration and tool schemas for exact options.
Discuss your setup