> ## 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.

# Continue or approve

> Answer a paused run’s question or approve its held action.


## OpenAPI

```yaml openapi.json post /v1/executions/{id}/continue
openapi: 3.1.0
info:
  title: Ocean One API
  version: 2.3.1
servers:
  - url: https://api.plungeai.com
paths:
  /v1/executions/{id}/continue:
    post:
      operationId: post-v1-executions-id-continue
      tags:
        - Executions
      summary: Answer a paused run’s question or approve its held action
      description: "`answer` replies to a question (or denies / redirects an approval); `approve: true` approves the pending action with the stored token. `allow_scope` (approve only): `once` this call, `run` the tool for the rest of the run, `always` is the bot’s stored rule (set it with PUT /v1/workflows/{id}/permissions); any other value is `once`. Runs inline: up to ~30 s while an approved action executes."
      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-…`)
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                answer:
                  type: string
                  maxLength: 65536
                approve:
                  type: boolean
                allow_scope:
                  type: string
                  enum:
                    - once
                    - run
                    - always
                format:
                  type: string
                  enum:
                    - json
                    - yaml
                    - markdown
                    - text
          text/yaml:
            schema:
              type: string
      responses:
        "200":
          description: The agent’s reply 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
                    description: The agent's reply
                  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"
                  conversation_recorded:
                    type: boolean
                    description: false when the turn ran but could not be saved to the thread (GET …/conversation lacks it); the reply is still returned
            text/yaml:
              schema:
                type: string
            text/markdown:
              schema:
                type: string
            text/plain:
              schema:
                type: string
        "400":
          description: "missing_answer — neither `answer` nor `approve: true`; invalid_params; invalid_format / invalid_json / invalid_yaml — unreadable body or unknown format"
          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_found — no route for this method on this path: every other method answers it"
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Error"
        "409":
          description: not_paused — the run already completed; use …/followup
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Error"
        "410":
          description: session_expired — no conversation session (expired, or not a conversational agent)
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Error"
        "502":
          description: continue_failed — the agent could not continue; retry; 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_…)"
```