Validate an orchestration graph
POST/v1/projects/:project_id/orchestrations/validate
Statically validates an orchestration graph without persisting anything. Checks that every node has its required field, node ids are unique, edges reference existing nodes, the graph is acyclic (unless it contains a loop node), and every input_mapping {"var": "..."} reference resolves to a state key written by an upstream node or seeded by input_schema. Returns blocking problems and non-blocking warnings (e.g. a state key only written on a conditional branch). The same checks are enforced on create and update, which fail with 400 ORCHESTRATION_VALIDATION_FAILED listing the same items under meta.problems and meta.warnings.
Request
Responses
- 200
- 400
- 401
- 404
- 413
- 429
- 500
- 502
- 4XX
Validation result
The request was malformed or failed validation.
Unauthorized
The project does not exist or the caller is not a member of it (RESOURCE_NOT_FOUND).
REQUEST_REJECTED — the request body is over the size the body parser accepts
QUOTA_EXCEEDED — a requests quota on the calling API key or its project is spent for the window; Retry-After says when it reopens
Response Headers
Seconds until the quota window admits a request again
Unexpected server error — INTERNAL_ERROR, with the raw message never forwarded
The deployment's admission service is asked about this write and did not answer — ADMISSION_UNAVAILABLE; the write did not happen
The deployment's admission service refused this write — answered under the service's own 4xx status, with its code (matching ^[A-Za-z_][A-Za-z0-9_]{0,63}$, not necessarily an ERROR_CODES key), message and meta; the write did not happen. A status this operation also declares on its own is documented there