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

# Run a command and wait for it to finish

> Runs a command to completion and returns its full output in a single
response. For live output use `POST /exec/stream` (Server-Sent Events)
or `GET /exec/connect` (WebSocket). A non-zero exit code is returned in
the body, not as an HTTP error. The sandbox must be `running`; a paused
sandbox returns `503`. Activate it first with
`POST /sandboxes/{sandbox_id}/activate` (the SDKs do this automatically).




## OpenAPI

````yaml https://raw.githubusercontent.com/superserve-ai/sandbox/refs/heads/main/api/openapi.yaml post /exec
openapi: 3.1.0
info:
  title: Superserve API
  version: 0.1.0
  description: >
    Superserve provides sandbox infrastructure to run AI agents in the cloud.
    Powered by Firecracker MicroVMs.


    ## Sandbox lifecycle


    ```

    active <--> paused --> deleted

    ```


    A sandbox is `active` when running and `paused` after being paused. Resuming

    a paused sandbox returns it to `active`. Deleting releases all resources.


    | Endpoint | What it does |

    |----------|-------------|

    | `POST /sandboxes` | Create a new sandbox (optionally `from_template`) |

    | `PATCH /sandboxes/:id` | Partially update a running sandbox (e.g. network
    rules) |

    | `POST /sandboxes/:id/pause` | Snapshot full state, suspend the VM |

    | `POST /sandboxes/:id/resume` | Restore from snapshot, continue where it
    left off |

    | `DELETE /sandboxes/:id` | Delete sandbox and all resources |


    ## Sandbox environment


    By default sandboxes boot from the curated `superserve/base` template
    (Ubuntu 24.04,

    1 vCPU, 1 GB RAM, 4 GB disk, with Python 3.12, Node.js 22, npm, git, curl,

    and build-essential pre-installed). Callers can override with any template

    name (e.g. `superserve/python-3.11`, `superserve/node-22`) or a team-owned
    template UUID

    via the `from_template` field on `POST /sandboxes`.


    ## Files and commands


    `/files`, `/exec`, and `/exec/stream` run against a single sandbox and use

    its `X-Access-Token` (returned by create, resume, and activate), not the

    team API key. Two host forms reach them:


    - `https://sandbox.superserve.ai/...` with `X-Superserve-Sandbox-Id:
    <sandbox_id>`.

    - `https://boxd-{sandbox_id}.sandbox.superserve.ai/...` — no routing header
    needed.
  contact:
    name: Superserve Team
  license:
    name: Proprietary
servers:
  - url: https://api.superserve.ai
    description: Production
security: []
paths:
  /exec:
    servers:
      - url: https://sandbox.superserve.ai
        description: Shared host — send the sandbox ID in `X-Superserve-Sandbox-Id`.
      - url: https://boxd-{sandbox_id}.sandbox.superserve.ai
        description: Per-sandbox host.
        variables:
          sandbox_id:
            default: ''
            description: The sandbox ID.
    post:
      tags:
        - Exec
      summary: Run a command and wait for it to finish
      description: >
        Runs a command to completion and returns its full output in a single

        response. For live output use `POST /exec/stream` (Server-Sent Events)

        or `GET /exec/connect` (WebSocket). A non-zero exit code is returned in

        the body, not as an HTTP error. The sandbox must be `running`; a paused

        sandbox returns `503`. Activate it first with

        `POST /sandboxes/{sandbox_id}/activate` (the SDKs do this
        automatically).
      operationId: execRun
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ExecRequest'
      responses:
        '200':
          description: The command finished; full output and exit code.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ExecResult'
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '404':
          $ref: '#/components/responses/NotFound'
        '500':
          $ref: '#/components/responses/InternalError'
        '503':
          $ref: '#/components/responses/ServiceUnavailable'
      security:
        - accessToken: []
components:
  schemas:
    ExecRequest:
      type: object
      required:
        - command
      properties:
        command:
          type: string
          minLength: 1
          description: >-
            Command to execute. Wrapped in `/bin/sh -c` unless `args` is
            provided.
        args:
          type: array
          items:
            type: string
          description: >-
            If provided, `command` is used as the binary and `args` as arguments
            (no shell wrapping).
        env:
          type: object
          additionalProperties:
            type: string
          description: Environment variables for the command.
        working_dir:
          type: string
          description: Working directory (default `/home/user`).
        timeout_s:
          type: integer
          default: 30
          description: Timeout in seconds.
    ExecResult:
      type: object
      description: Full output of a command run to completion via `POST /exec`.
      required:
        - stdout
        - stderr
        - exit_code
      properties:
        stdout:
          type: string
          description: Complete standard output.
        stderr:
          type: string
          description: Complete standard error.
        exit_code:
          type: integer
          description: Process exit code. A non-zero value is returned, not raised.
    Error:
      type: object
      description: |
        Error envelope. `error.code` is a stable, machine-readable identifier
        (e.g. `bad_request`, `not_found`, `conflict`, `rate_limited`,
        `too_many_builds`, `too_many_templates`, `too_many_sandboxes`,
        `image_pull_failed`, `step_failed`, `snapshot_failed`,
        `start_cmd_failed`, `ready_cmd_failed`, `build_failed`).
        `error.message` is human-readable and may change between releases;
        clients should branch on `code`, not `message`.
      properties:
        error:
          type: object
          properties:
            code:
              type: string
            message:
              type: string
  responses:
    BadRequest:
      description: Invalid request
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    Unauthorized:
      description: Missing or invalid API key
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    NotFound:
      description: Resource not found
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    InternalError:
      description: Internal server error
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    ServiceUnavailable:
      description: >
        The sandbox is not currently running (for example, paused) or is
        temporarily unavailable. For a paused sandbox, activate it with `POST
        /sandboxes/{sandbox_id}/activate` and retry; the SDKs do this
        automatically.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  securitySchemes:
    accessToken:
      type: apiKey
      in: header
      name: X-Access-Token
      description: >
        Per-sandbox token returned by create, resume, and activate. Grants
        access to a single sandbox's files and commands. Distinct from the team
        `X-API-Key`.

````