What is wrong with this graph, without saving it
POST/api/flows/validate
The editor's live markers.
Takes a DEFINITION rather than a flow id, because the canvas asks while the author is still typing and the answer has to describe the graph in front of them rather than the last one they saved.
Reports BOTH severities, which a save structurally cannot: a 422 carries only what blocks.
errorblocks a save. Reserved for a graph that cannot be right in any state of construction — a branch pointing at a node that does not exist, two options sharing a value so the second is unreachable, a node kind this deployment cannot run.warningsaves. Everything merely unfinished lives here: an unreachable node, a half-wired condition, a button with no option behind it yet. Blocking those would make the editor refuse the normal middle of building a flow.
The same FlowValidator answers here and at the save gate. A second
copy of these rules in the panel is the drift that produced the
phantom-node palette.
Request
Responses
- 200
- 401
- 403
- 422
Every finding, both severities.
Not authenticated. code: account_disabled means the member's seat was deactivated in this workspace: the session is over even though the token was not revoked (clients sign out and clean up).
Authenticated but not allowed.
The request failed validation.