> ## 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 latest telemetry for many machines > Returns the most recent telemetry sample for up to 5,000 node and VM IDs combined. A machine with no sample inside your reservation window is omitted. If any ID is not visible to your organization, the whole request returns 404; split requests by reservation to isolate failures. Send large ID sets in parallel chunks rather than one at a time. ## OpenAPI ````yaml openapi.yaml POST /v1/observability/nodes/telemetry/latest 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/observability/nodes/telemetry/latest: post: tags: - Monitoring summary: Get latest telemetry for many machines description: >- Returns the most recent telemetry sample for up to 5,000 node and VM IDs combined. A machine with no sample inside your reservation window is omitted. If any ID is not visible to your organization, the whole request returns 404; split requests by reservation to isolate failures. Send large ID sets in parallel chunks rather than one at a time. operationId: platformBatchLatestTelemetry requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/PlatformTelemetryBatchRequest' example: node_ids: - 33333333-3333-4333-8333-333333333333 virtual_machine_ids: - 66666666-6666-4666-8666-666666666666 responses: '200': description: Latest samples for the visible machines. content: application/json: schema: $ref: '#/components/schemas/PlatformTelemetryBatch' example: nodes: - node_id: 33333333-3333-4333-8333-333333333333 observed_at: '2026-10-14T12:00:00Z' samples: 1 values: observed_at: '2026-10-14T12:00:00Z' gpu_utilization: '87.5' gpu_temperature: '64' cpu_utilization: '22.1' memory_utilization: '41.0' - virtual_machine_id: 66666666-6666-4666-8666-666666666666 observed_at: '2026-10-14T12:00:05Z' samples: 1 values: observed_at: '2026-10-14T12:00:05Z' gpu_utilization: '12.0' '400': description: An ID is not a UUID, or more than 5,000 IDs were sent. content: application/json: schema: $ref: '#/components/schemas/PlatformPlainError' example: error: too_many_node_ids '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/PlatformMachineNotVisible' default: $ref: '#/components/responses/Error' components: schemas: PlatformTelemetryBatchRequest: type: object properties: node_ids: type: array items: type: string format: uuid virtual_machine_ids: type: array items: type: string format: uuid PlatformTelemetryBatch: type: object properties: nodes: type: array items: type: object properties: node_id: type: string format: uuid description: Present for a physical node. virtual_machine_id: type: string format: uuid description: Present for a VM. observed_at: type: string format: date-time samples: type: integer values: type: object additionalProperties: type: string PlatformPlainError: type: object description: Error body with a machine-readable string. Check the HTTP status first. required: - error properties: error: type: string 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' PlatformMachineNotVisible: description: >- The machine is not in a reservation your organization holds, or the reservation was cancelled. content: application/json: schema: $ref: '#/components/schemas/PlatformPlainError' example: error: not_found 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.