Trigger public workflow version
Trigger a public or unlisted workflow using the organization nickname, workflow slug, and version.
Authentication required - provide your API key as api_key in the request body.
Example:
POST /api/v1/public/@acme-corp/workflows/my-generator/versions/v1/trigger
Body: { "api_key": "your-api-key", "inputs": { "prompt": "..." } }
Path Parameters
Organization nickname (without @ prefix)
"acme-corp"
Workflow slug
"my-image-generator"
Version identifier
"v1"
Body
Your eachlabs API key. The public trigger authenticates via this body field instead of an Authorization header.
"your-api-key"
Optional: Specific version to trigger.
If not provided, triggers the latest version of the workflow. This allows you to execute specific versions for testing or comparison.
"v1"
Input parameters defined in the workflow definition for the workflow
Optional webhook URL for execution completion notifications.
When provided, the engine will POST an ExecutionDetails payload to this URL
when the workflow finishes (either successfully or with an error).
See the Webhooks section for detailed information about webhook behavior and payload structure.
"https://your-api.com/webhooks/workflow-completed"
Response
Workflow execution started
Response from triggering a workflow execution
Unique execution identifier (only present for successful triggers)
"exec_xyz789"
Execution status immediately after triggering.
queued: Workflow execution has been queued and will start shortlyfailed: Trigger failed due to validation or system error
queued, failed "queued"
RFC3339 timestamp when the execution was queued (only present for successful triggers)
Error message (only present when status is "failed")
"invalid input: missing required field"