Post Manifests
POST/v1/manifests
Register a worker, step, or saga manifest. Accepts YAML or JSON body.
Body must define a mapping with kind (worker | step | saga) and kind-specific
fields. Same schema as the file-based manifests used by the CLI.
Pass dry_run=true to validate without writing catalog rows (CI / preflight).
Returns:
ManifestDeployResponse with a success message (and dry_run echoed).
Raises: HTTPException: 413 when body is too large; 400 on invalid body, unknown kind, or missing worker/step dependencies.
Request
Responses
- 200
- 400
- 404
- 409
- 413
- 415
- 422
Successful Response
Manifest validation failed (invalid YAML/JSON, unknown kind, schema errors).
Referenced catalog definition (worker/step/saga) is missing.
Referenced catalog definition exists but is inactive (INACTIVE_CATALOG_DEFINITION).
Manifest body exceeds MANIFEST_MAX_BODY_BYTES.
Unsupported Content-Type; use application/json or YAML media types.
Validation Error