Trigger workflow execution
Start an asynchronous workflow execution through api-service. This route forwards to workflows-engine and requires callers to pin the workflow version in the path.
The immediate response only confirms the workflow was queued. Downstream workflow
lifecycle statuses are running, completed, failed, and cancelled.
api-service does not expose workflows-engine’s bulk trigger route.
Documentation Index
Fetch the complete documentation index at: https://docs.eachlabs.ai/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
API key for authentication
Path Parameters
Workflow ID or slug to execute.
Workflow version ID to execute.
Query Parameters
Optional compatibility query parameter for execution completion webhooks. The request body field takes precedence when both are present.
Body
Input values defined by the workflow version. May be omitted for workflows with no inputs.
{
"prompt": "A cinematic establishing shot of a mountain lake"
}Optional webhook URL for workflow execution completion.
"https://your-app.com/webhook"
Optional secret used to sign workflow webhook requests.
"your-secret-key"