Skip to main content
POST
Check a flow config without saving
Runs the same checks a save runs, including the normalisation a save applies first. Always 200: an invalid config is a valid answer to “would this be accepted?”. Nothing is persisted. warnings lists what saves but may not do what you meant, such as a condition branch with no Output step; warnings never make a config invalid.

Headers

x-apikey
string
required

API Key for authentication

Body

application/json
config
Config · object
required

Flow definition, possibly unsaved: {inputs: [...], nodes: [...], output: {...}}. Same shape POST /v1/flows and GET /v1/flows/{flow_id} use.

Response

Whether the config would be accepted on save

valid
boolean
required
errors
FlowConfigError · object[]

Why the config would be rejected on save. Empty when valid is true.

warnings
FlowConfigError · object[]

What the config's author should know although it saves: a condition branch with no Output step (its rows return nothing), a Custom JSON response without the declared output fields. Never affects valid.