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

# List your Spot orders

> Lists your organization's 200 most recent bids (resting, running, cancelled, and ended) and the asks your relisted capacity has on the books. Poll this or getSpotOrder to follow a bid.

CLI equivalent: `ornn spot orders`.


## OpenAPI

````yaml openapi.yaml GET /v1/markets/spot/orders
openapi: 3.1.0
info:
  title: Ornn compute API
  version: 1.0.0
  description: >-
    Customer HTTP API for Ornn GPU capacity. It covers reserved capacity and
    nodes, VM and Bare Metal access, Kubernetes and Slurm clusters, SSH keys,
    storage volumes and GitHub repositories, private networks, monitoring,
    buying and selling capacity (Reserve, Market, Spot, and Relist), and
    billing. API keys are scoped to one organization and act with their
    creator's access there; account, team, and API-key management stay in the
    console. Most operations require an approved organization. See
    https://docs.ornn.com/api-keys to create a key and
    https://docs.ornn.com/guides/kubernetes-api for an end-to-end Kubernetes
    integration. Examples use fictional IDs and credentials. The info.version
    field identifies the contract revision, not a shared API path version.
  contact:
    email: support@ornn.com
servers:
  - url: https://api.ornn.com
    description: Production
security:
  - OrnnApiKey: []
tags:
  - name: Authentication
  - name: Reservations
  - name: GPU nodes
  - name: Clusters
  - name: Workers
  - name: Virtual machines
    description: >-
      Choose a VM disk, launch VM access on a reservation, and read each VM's
      status, launch progress, and SSH connection details.
  - name: Bare Metal
    description: >-
      Launch Bare Metal access on a reservation, read a host's readiness and SSH
      connection details, and reboot or hard reset it.
  - name: SSH keys
    description: >-
      Register public keys for your organization, choose which keys a VM or Bare
      Metal reservation uses, and queue key delivery to machines. Slurm clusters
      take organization key IDs at launch. Kubernetes API access does not use
      SSH keys.
  - name: Reserve
    description: >-
      Browse reserved-capacity listings and their terms, and post, cancel, or
      accept offers. Reserve listings are visible to approved organizations.
  - name: Market
    description: >-
      Browse relisted capacity and buy windows at the asking price, paid up
      front. Open to every member of your organization.
  - name: Spot
    description: >-
      Hourly order books for VMs with 1, 2, 4, or 8 GPUs on one node: read
      books, trades, and quotes, place and cancel bids, and follow fills.
  - name: Relist
    description: >-
      Sell whole nodes from a reservation you hold at your asking price, and
      manage those listings.
  - name: Storage
    description: >-
      Managed volumes, their files, and GitHub repository pulls. Volumes belong
      to the API key's creator in the key's organization.
  - name: Networks
    description: >-
      Organization private networks and the WireGuard configs you use to reach
      private machines and clusters.
  - name: Monitoring
    description: >-
      Machine telemetry and console logs for capacity your organization holds.
      Reads are limited to your reservation window.
  - name: Billing
    description: >-
      Invoices, billing summary, usage cost, Ornn credits, and account
      statements. Saving a card and paying invoices stay in the console.
externalDocs:
  description: REST integration walkthrough
  url: >-
    https://docs.ornn.com/guides/kubernetes-access#provision-and-manage-through-rest
paths:
  /v1/markets/spot/orders:
    get:
      tags:
        - Spot
      summary: List your Spot orders
      description: >-
        Lists your organization's 200 most recent bids (resting, running,
        cancelled, and ended) and the asks your relisted capacity has on the
        books. Poll this or getSpotOrder to follow a bid.
      operationId: capacityListSpotOrders
      responses:
        '200':
          description: Your orders.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CapacitySpotOrderList'
              example:
                orders:
                  - orderId: aaaaaaaa-aaaa-4aaa-8aaa-aaaaaaaaaaaa
                    orderBookId: bbbbbbbb-bbbb-4bbb-8bbb-bbbbbbbbbbbb
                    gpuSlug: nvidia_h100_sxm
                    side: bid
                    orderType: limit
                    pricePerGpuHourMicroUsd: 2500000
                    requestedGpus: 8
                    remainingGpus: 0
                    status: running
                    cancelReason: null
                    aggressorSide: bid
                    listingId: eeeeeeee-eeee-4eee-8eee-eeeeeeeeeeee
                    nodeId: 33333333-3333-4333-8333-333333333333
                    createdAt: '2026-10-14T18:30:00.000Z'
                    filledAt: '2026-10-14T18:30:00.000Z'
                    endedAt: null
                    endReason: null
                    isMine: true
                    isSeller: false
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        default:
          $ref: '#/components/responses/Error'
components:
  schemas:
    CapacitySpotOrderList:
      type: object
      required:
        - orders
      properties:
        orders:
          type: array
          description: >-
            Your organization's 200 most recent bids, then the asks your
            listings have on the books. Recently finished orders are retained
            for a limited time.
          items:
            $ref: '#/components/schemas/CapacitySpotOrder'
    CapacitySpotOrder:
      type: object
      required:
        - orderId
        - side
        - status
        - isMine
        - isSeller
      properties:
        orderId:
          type: string
          format: uuid
          description: Order ID. A filled bid's reservation has this same ID.
        orderBookId:
          type: string
          format: uuid
        gpuSlug:
          type:
            - string
            - 'null'
        side:
          type: string
          enum:
            - bid
            - ask
          description: bid for your bids; ask for capacity your listings offer on the book.
        orderType:
          type: string
          enum:
            - limit
            - market
        pricePerGpuHourMicroUsd:
          type:
            - integer
            - 'null'
          format: int64
          description: >-
            The order's own price: a bid's limit, or null for a market bid. A
            fill's price is on the reservation.
        requestedGpus:
          type:
            - integer
            - 'null'
        remainingGpus:
          type:
            - integer
            - 'null'
        status:
          type: string
          description: >-
            Bids: resting (waiting on the book), running (filled; the spot
            reservation is live), cancelled (never filled), or ended (a running
            reservation stopped). Asks: resting, exhausted, or cancelled. Handle
            unrecognized values.
        cancelReason:
          type:
            - string
            - 'null'
          description: >-
            For example unfilled_market_order, cancelled_by_owner, or
            cancelled_by_admin.
        aggressorSide:
          type:
            - string
            - 'null'
          enum:
            - bid
            - ask
            - null
        listingId:
          type:
            - string
            - 'null'
          format: uuid
          description: The listing that filled the bid.
        nodeId:
          type:
            - string
            - 'null'
          format: uuid
          description: The node the filled bid runs on.
        createdAt:
          type:
            - string
            - 'null'
          format: date-time
        filledAt:
          type:
            - string
            - 'null'
          format: date-time
        endedAt:
          type:
            - string
            - 'null'
          format: date-time
        endReason:
          type:
            - string
            - 'null'
          description: >-
            Why a running bid ended: stopped_by_buyer, stopped_by_seller,
            stopped_by_admin, preempted_by_reservation, listing_ended,
            payment_failed, or provisioning_failed. Handle unrecognized values.
        failure:
          type:
            - object
            - 'null'
          description: >-
            Customer-facing failure details for an ended order with a payment or
            provisioning failure. Visible only to the buyer and staff; derived
            from endReason.
          required:
            - code
            - message
          properties:
            code:
              type: string
            message:
              type: string
        isMine:
          type: boolean
          description: True when your organization placed this order.
        isSeller:
          type: boolean
          description: >-
            True when the order filled against, or is, capacity your
            organization listed.
    Error:
      type: object
      properties:
        code:
          type: string
        detail:
          oneOf:
            - type: string
            - type: object
              required:
                - code
                - message
              properties:
                code:
                  type: string
                message:
                  type: string
  responses:
    Unauthorized:
      description: >-
        The credential is missing, invalid, revoked, or no longer belongs to a
        current organization member. Check the HTTP status before parsing the
        body.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    Forbidden:
      description: >-
        The credential lacks access to this operation, or the organization
        requires approval. An API key does not bypass these checks.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    Error:
      description: >-
        Unsuccessful request. Check HTTP status first. Errors may have
        detail.code/detail.message, a string detail and optional top-level code,
        or an empty/non-JSON body. 401: invalid credential; 403: access or
        approval required; 404: not visible or credentials not ready; 409:
        lifecycle conflict; 429: back off; 5xx: service failure. Inspect current
        state before retrying mutations.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  securitySchemes:
    OrnnApiKey:
      type: http
      scheme: bearer
      bearerFormat: ornn_sk_...
      description: >-
        Create an organization API key in Account Settings > Developer. Do not
        send this key to the Kubernetes API server.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.