Validate an automation primitive input
Checks the selected primitive input through its validation implementation after scope and input-dependent permission checks. The body follows the same discovered input schema as invocation; the operation itself is not invoked. A valid result normally contains data.valid=true and meta.dry_run=true, while validation failures identify the offending fields.
Authorizations
Passport bearer token authentication for legacy admin sessions.
Path Parameters
Exact dot-separated operation name returned by primitive discovery; route names accept lowercase letters, underscores and dots.
^[a-z._]+$Body
Input accepted by the selected primitive.
Operation-specific input object; use GET /primitives/{name}/schema to discover its properties and required fields.
Response
Operation result; data and metadata follow the selected primitive contract.
The PrimitiveResult envelope serialized by primitive invocation and validation.
Whether the selected primitive succeeded.
true
Operation-specific JSON result, or null on failure. Its schema is returned by primitive discovery.
Domain errors or validation field errors.
Non-fatal operation warnings.
Operation metadata; may contain status, dry_run, replay information or pagination. Empty metadata serializes as an empty array.