> ## Documentation Index
> Fetch the complete documentation index at: https://docs.plungeai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Get the output

> The run’s final output (json, yaml, markdown or text).


## OpenAPI

```yaml openapi.json get /v1/executions/{id}/output
openapi: 3.1.0
info:
  title: Ocean One API
  version: 2.3.1
servers:
  - url: https://api.plungeai.com
paths:
  /v1/executions/{id}/output:
    get:
      operationId: get-v1-executions-id-output
      tags:
        - Executions
      summary: The run’s final output (json, yaml, markdown or text)
      description: The stored result of the final task. `format=text` is the bare content, `markdown` what the MCP plane renders, `json`/`yaml` the envelope.
      security:
        - ozkBearer: []
      parameters:
        - name: id
          in: path
          required: true
          schema:
            type: string
          description: Execution id (the x-execution-id of the run, or its engine id `exec-…`)
        - name: format
          in: query
          schema:
            type: string
            enum:
              - json
              - yaml
              - markdown
              - text
          description: Response format; overrides Accept (an unknown value is 400 invalid_format)
        - name: on_behalf_of
          in: query
          schema:
            type: string
            minLength: 1
            maxLength: 128
          description: 'Read a run that was made on a customer’s behalf (POST /v1/execute with `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.'
      responses:
        "200":
          description: 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.
          content:
            application/json:
              schema:
                type: object
                properties:
                  execution_id:
                    type: string
                  status:
                    type: string
                    description: running | completed | incomplete | failed | cancelled, or needs_input / needs_approval when the run finished its turn and waits for the user (POST …/continue)
                  content:
                    type: string
                  final_task_id:
                    type:
                      - string
                      - "null"
                  steps:
                    type: array
                    description: Every step of a multi-task run; the output is the final one’s
                    items:
                      type: object
                      properties:
                        task_id:
                          type: string
                        agent:
                          type:
                            - string
                            - "null"
                        final:
                          type: boolean
                  continuation:
                    type:
                      - object
                      - "null"
                    description: Non-null when the run is paused awaiting the user
                    properties:
                      status:
                        type: string
                        enum:
                          - question
                          - needs_approval
                      agent:
                        type: string
                      question:
                        type:
                          - string
                          - "null"
                      pending_action:
                        type:
                          - object
                          - "null"
                        description: "The held action: summary, price, and the permission class / tool when known"
            text/yaml:
              schema:
                type: string
            text/markdown:
              schema:
                type: string
            text/plain:
              schema:
                type: string
        "400":
          description: invalid_on_behalf_of — not a valid customer id
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Error"
        "401":
          description: unauthorized — missing, invalid or revoked ozk_ key
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Error"
        "404":
          description: "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"
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Error"
        "409":
          description: execution_failed — the run failed; the message is its error
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Error"
        "410":
          description: result_expired — the run completed but its stored result is gone
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Error"
        "502":
          description: upstream_error — a store failed; no detail is returned, retry shortly
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Error"
components:
  schemas:
    Error:
      type: object
      description: Standard error envelope. Every error response also carries an `X-Error-Code` response header equal to error.code, so a client branches on the header regardless of the negotiated body format (json | yaml | markdown | text). When the request created an execution, the `X-Execution-Id` response header is also set. Errors follow the negotiated format like success bodies.
      properties:
        error:
          type: object
          properties:
            code:
              type: string
            message:
              type: string
            connect:
              type: object
              description: "On a 424 connection_required / credential_required: where the missing connection is made."
              properties:
                provider:
                  type: string
                method:
                  type: string
                  enum:
                    - oauth
                    - api_key
                    - wallet
                link:
                  type: string
                  example: POST /v1/connections/stripe/link
          required:
            - code
            - message
          additionalProperties: true
      required:
        - error
  securitySchemes:
    ozkBearer:
      type: http
      scheme: bearer
      description: "ozk_ platform API key (Authorization: Bearer ozk_…)"
```