Executions
Trigger, monitor, and control workflow executions.
Executions
All endpoints scoped to: /v1/workspaces/:workspaceId/spaces/:spaceId/executions.
Endpoints
POST /v1/workspaces/:wId/spaces/:sId/executions
Manually trigger a workflow execution.
Body
Response 201
GET /v1/workspaces/:wId/spaces/:sId/executions
List executions.
Query params
| Param | Type | Description |
|---|---|---|
workflowId | uuid | Filter by workflow |
status | string | pending | running | completed | failed | cancelled | suspended |
Response 200: array of execution objects
GET /v1/workspaces/:wId/spaces/:sId/executions/:id
Get a single execution with full output and error details.
Response 200
GET /v1/workspaces/:wId/spaces/:sId/executions/:id/logs
Get step-by-step logs for an execution.
Response 200: array of log entries
GET /v1/workspaces/:wId/spaces/:sId/executions/:id/events (SSE)
Stream live execution events using Server-Sent Events. Closes automatically after 10 minutes.
Example
PATCH /v1/workspaces/:wId/spaces/:sId/executions/:id/respond
Respond to a suspended execution waiting for human input.
Body
Response 200
PATCH /v1/workspaces/:wId/spaces/:sId/executions/:id/approve
Shorthand approve: equivalent to respond with { "approved": true }.
Response 200
DELETE /v1/workspaces/:wId/spaces/:sId/executions/:id
Cancel an execution. Most reliable when status = pending.
Response 204
Cancellation is best-effort for running executions: the worker may already be mid-step.