Skip to main content
POST
Submit Workflow

Authorizations

X-API-Key
string
header
required

API key for authentication.

Body

application/json

Request to submit a workflow that runs independently of your connection.

Runs submitted this way are always stored, so persistence_mode is not accepted here. Read the result with the execution retrieval endpoint, and delete the run when you no longer need it.

template
required

Template ID (string) or inline template definition (object).

execution_id
string | null

Provide the ID of a run that stopped before it finished — one you cancelled, or one that ended in an error — to continue it from where it stopped. A run that is still in progress, or that already completed, cannot be continued and returns 409.

input
Input · object | null

Input values for template placeholders.

model_name
enum<string>
default:base

Selects the model capability tier. Use "base" for the default routing strategy, or "pro" to allow the most capable available model when higher reasoning or accuracy is required. Model selection is dynamic and may vary based on task type, availability, and failover.

Available options:
base,
pro
time_range

Predefined rolling time windows for filtering data.

Available options:
last_24_hours,
last_7_days,
last_30_days,
last_60_days,
last_90_days,
last_180_days,
last_365_days

Response

The workflow was accepted and is now running.

Acknowledgement that a workflow was accepted and is now running.

execution_id
string
required

Identifier for the submitted run. Use it to poll for status, stream events, cancel, and retrieve the result.

status
enum<string>
required

Lifecycle status of the run at submission time.

Available options:
pending,
running,
completed,
error,
cancelled