Workflows
Execute a saved workflow
Run one of your saved workflows by id with an optional `input` or `inputs`.
Headers: every response carries x-request-id (quote it in support requests). Send x-trace-id (optional, a UUID) to correlate this call across planes; reusing an id that already ran answers 409 duplicate_execution_id. Pick the body format with format or Accept (application/json, text/yaml, text/markdown, text/plain).
Authorization: send Authorization: Bearer $PLUNGE_API_KEY; X-API-Key: <ozk_ key> is accepted as an alternative.
Authorizations
Authorization: Bearer ozk_…. ozk_ platform API key (Authorization: Bearer ozk_…)Path parameters
Body
application/jsonAvailable options: json, yaml, markdown, text
Response
Engine acknowledgement Response format negotiates via the format field, an Accept header (application/json, text/yaml, text/markdown, text/plain), or the request Content-Type mirror; default JSON.
application/jsontext/yamltext/markdowntext/plain
Response headers
invalid_json / invalid_yaml / invalid_body — unreadable body; invalid_format — format must be one of json, yaml, markdown, text
application/json
unauthorized — missing, invalid or revoked ozk_ key
Error code: unauthorizedfrom code
application/json
workflow_not_found — no saved workflow with that id for this key; unknown_agent — the saved workflow names an agent the registry does not know (refused pre-dispatch); not_found — no route for this method on this path: every other method answers it
application/json
duplicate_execution_id — x-trace-id already used by an earlier run — send a fresh UUID; not_executable — the id names a saved campus or building document, which is compiled by POST /v1/companies/{campus}/apply, never executed
application/json
payload_too_large — body over 1 MiB (MAX_REQUEST_SIZE)
application/json
rate_limited — Retry-After header
application/json
engine_error
application/json