> ## 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. # Get a fill > Returns one fill your organization bought, or one sold from capacity you listed. A fill's `fillId` is also its reservation ID. Use it with [Get a reservation](/api-reference/reservations/get.md) to see its nodes and VMs. ## OpenAPI ````yaml openapi.yaml GET /v1/markets/fills/{fillId} 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, order books, 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: Order books description: >- Hourly order books for whole nodes, one VM per node: read books, trades, and quotes, place and cancel bids, and follow and end 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/fills/{fillId}: get: tags: - Order books summary: Get a fill description: >- Returns one fill your organization bought, or one sold from capacity you listed. operationId: capacityGetFill parameters: - name: fillId in: path required: true description: Fill ID. It is also its reservation's ID. schema: type: string format: uuid example: dddddddd-dddd-4ddd-8ddd-dddddddddddd responses: '200': description: The fill. content: application/json: schema: $ref: '#/components/schemas/CapacityMarketFillEnvelope' example: fill: fillId: dddddddd-dddd-4ddd-8ddd-dddddddddddd orderId: aaaaaaaa-aaaa-4aaa-8aaa-aaaaaaaaaaaa gpuSlug: nvidia_h100_sxm saleType: spot region: us-east-11 pricePerGpuHourMicroUsd: 2650000 nodes: 2 gpus: 16 filledAt: '2026-10-14T18:30:00.000Z' isMine: true isSeller: false '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': description: The fill does not exist or is not visible to your organization. content: application/json: schema: $ref: '#/components/schemas/Error' example: detail: code: fill_not_found message: Ornn could not find that fill. default: $ref: '#/components/responses/Error' components: schemas: CapacityMarketFillEnvelope: type: object required: - fill properties: fill: $ref: '#/components/schemas/CapacityMarketFill' Error: type: object properties: code: type: string detail: oneOf: - type: string - type: object required: - code - message properties: code: type: string message: type: string CapacityMarketFill: type: object description: >- A trade. It never changes; its reservation, read from GET /commerce/reservations/{reservationId} with the fill ID, says whether it is still running. required: - fillId - pricePerGpuHourMicroUsd - nodes - gpus - isMine - isSeller properties: fillId: type: string format: uuid description: Fill ID. Its reservation has this same ID. orderId: type: - string - 'null' format: uuid description: The bid that bought it. gpuSlug: type: - string - 'null' saleType: type: - string - 'null' enum: - spot - on-demand - null region: type: - string - 'null' description: The region slug its VMs run at. pricePerGpuHourMicroUsd: type: integer format: int64 description: What the buyer pays per GPU-hour, fees included. nodes: type: integer description: The nodes its GPUs are on. gpus: type: integer description: GPUs bought. filledAt: type: - string - 'null' format: date-time isMine: type: boolean description: True when your organization bought it. isSeller: type: boolean description: True when it was sold from capacity your organization listed. 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.