Executions
Get the output
The run’s final output (json, yaml, markdown or text).
The stored result of the final task. format=text is the bare content, markdown what the MCP plane renders, json/yaml the envelope.
Authorizations
Authorization: Bearer ozk_…. ozk_ platform API key (Authorization: Bearer ozk_…)Path parameters
exec-…)Query parameters
Available options: json, yaml, markdown, text
on_behalf_of): its output sits under <your account>:cust:<id>. 1-128 characters of A-Z a-z 0-9 _ . - (no ".."); a bad value is 400 invalid_on_behalf_of. The run itself must still be yours. Honoured by the status, output and files reads only: continue, followup, steer, stream and conversation look under your own tenant.Minimum string length: 1 Maximum string length: 128
Response
Output 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
invalid_on_behalf_of — not a valid customer id
application/json
unauthorized — missing, invalid or revoked ozk_ key
application/json
execution_not_found — no execution with that id for this key (a foreign id answers the same); not_ready — the run is still going, retry; not_found — no route for this method on this path: every other method answers it
application/json
execution_failed — the run failed; the message is its error
application/json
result_expired — the run completed but its stored result is gone
application/json
upstream_error — a store failed; no detail is returned, retry shortly
application/json