Skip to main content
POST
Validate a flow definition without persisting

Authorizations

Authorization
string
header
required

JWT Bearer token authentication. Include your access token in the Authorization header as: Bearer YOUR_ACCESS_TOKEN

Example:

Path Parameters

flow_id
string<uuid>
required

Query Parameters

include_dynamic_data
boolean
default:false
include_output_schemas
boolean
default:false
include_default_reference_modes
boolean
default:false

Body

application/json

Model for flow definition update request.

definition
Definition · object
required

Flow definition in DSL format. The definition contains a 'flow' metadata object and a 'flow_configs' array with task configurations. Each task has a unique 'name' (UUID), 'task_executor_name' (the task type), 'task_title' (display name), 'parameters' (executor-specific config), and optional 'visual_properties' for UI layout. Tasks reference upstream outputs using '{{task_name.output_field}}' template syntax in their parameters to define dependencies.

Example:
expected_revision
string | null

Optional. The revision of the flow this write is based on, from the FlowResponse you last read or saved. When set, the write applies only if the latest version is still at that revision, checked under the flow lock; otherwise nothing is saved and the response is 409 with code revision_conflict and details.current_revision. Reload the flow, re-apply your change and retry. When omitted, the write applies on top of whatever is latest (last writer wins).

Response

Validation result returned

Response model for validate-only endpoint (no persistence).

validation_errors
ErrorDetails · object[]
required
default_reference_modes
Default Reference Modes · object | null
dynamic_data
Dynamic Data · object | null
ordered_task_names
string[] | null
output_schemas
Output Schemas · object | null