> ## 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. # Reboot or hard reset a Bare Metal host > Reboots a Bare Metal host. A reboot keeps your Linux user, home directory, SSH keys, and attached volumes. hard_reset wipes tenant data on the host (Linux user, home directory, authorized keys, and temporary files) and then reboots; Ornn restores the reservation's SSH keys afterward, so the reservation must have at least one. A reboot response includes reboot.status; poll the node until it is succeeded or failed, then confirm SSH. Another reboot request while one is in progress returns the existing reboot. Reuse the same request_id to retry safely without a second reboot. This route acts on hosts, not individual VMs: pass a node_id, never a VM id. To restart one VM, use POST /v1/orchestrator/nodes/{node_id}/virtual-machines/{vm_id}/reboot. Nodes in a Kubernetes or Slurm cluster cannot be rebooted here. CLI equivalents: `ornn machines reboot ` and `ornn machines reset --erase-local-data`. ## OpenAPI ````yaml openapi.yaml POST /v1/orchestrator/nodes/{node_id}/reboot 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/orchestrator/nodes/{node_id}/reboot: post: tags: - Bare Metal summary: Reboot or hard reset a Bare Metal host description: >- Reboots a Bare Metal host. A reboot keeps your Linux user, home directory, SSH keys, and attached volumes. hard_reset wipes tenant data on the host (Linux user, home directory, authorized keys, and temporary files) and then reboots; Ornn restores the reservation's SSH keys afterward, so the reservation must have at least one. A reboot response includes reboot.status; poll the node until it is succeeded or failed, then confirm SSH. Another reboot request while one is in progress returns the existing reboot. Reuse the same request_id to retry safely without a second reboot. This route acts on hosts, not individual VMs: pass a node_id, never a VM id. To restart one VM, use POST /v1/orchestrator/nodes/{node_id}/virtual-machines/{vm_id}/reboot. Nodes in a Kubernetes or Slurm cluster cannot be rebooted here. operationId: accessRebootNode parameters: - name: node_id in: path required: true description: >- A Bare Metal host node_id from the reservation's node list. Not a VM id. schema: type: string format: uuid example: 33333333-3333-4333-8333-333333333333 requestBody: required: false description: Omit the body for a plain reboot. content: application/json: schema: $ref: '#/components/schemas/AccessRebootRequest' example: mode: reboot request_id: reboot-2026-10-16-a responses: '200': description: >- The reboot or hard reset was queued. This does not mean the host is back. content: application/json: schema: $ref: '#/components/schemas/AccessRebootResult' example: id: 33333333-3333-4333-8333-333333333333 node_id: 33333333-3333-4333-8333-333333333333 reservation_id: 11111111-1111-4111-8111-111111111111 packet_id: 99999999-9999-4999-8999-999999999999 mode: reboot reboot: packet_id: 99999999-9999-4999-8999-999999999999 status: in_progress started_at: '2026-10-16T14:00:00Z' detail: null '400': description: The mode is not reboot or hard_reset. content: application/json: schema: $ref: '#/components/schemas/Error' example: detail: code: invalid_reboot_mode message: Choose reboot or hard reset. '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': description: The node is absent or not in an owned reservation. content: application/json: schema: $ref: '#/components/schemas/Error' example: detail: code: node_not_found message: Ornn could not find that node in this cluster. '409': description: >- The node is a cluster worker, a reboot is already in progress, a hard reset has no SSH key to restore, or the reservation cannot be used in its current state. content: application/json: schema: $ref: '#/components/schemas/Error' example: detail: code: reboot_in_progress message: >- This node is already rebooting. Wait for it to finish before requesting another action. '422': description: Ornn could not queue the reboot. Retry with the same request_id. content: application/json: schema: $ref: '#/components/schemas/Error' example: detail: code: reboot_enqueue_failed message: >- Ornn could not send the reboot to this machine. Try again in a moment. default: $ref: '#/components/responses/Error' components: schemas: AccessRebootRequest: type: object properties: mode: type: string enum: - reboot - hard_reset default: reboot description: >- reboot keeps data on the host. hard_reset wipes tenant data on the host before rebooting. request_id: type: - string - 'null' description: >- Optional client token. A repeated request with the same request_id returns the original request instead of rebooting again. AccessRebootResult: type: object required: - id - node_id - reservation_id - packet_id - mode properties: id: type: string format: uuid description: The ID you passed in the path. node_id: type: string format: uuid description: The host node being rebooted. reservation_id: type: string format: uuid packet_id: type: string format: uuid description: Identifier of the queued request. mode: type: string enum: - reboot - hard_reset reboot: description: Reboot progress, or null for a hard reset. oneOf: - type: 'null' - $ref: '#/components/schemas/AccessRebootStatus' Error: type: object properties: code: type: string detail: oneOf: - type: string - type: object required: - code - message properties: code: type: string message: type: string AccessRebootStatus: type: object description: Progress of a host reboot. Hard resets are not tracked here. required: - packet_id - status - started_at properties: packet_id: type: string format: uuid description: Identifier of the reboot request. status: type: string enum: - in_progress - succeeded - failed started_at: type: string format: date-time detail: description: Why the reboot failed, when status is failed. oneOf: - type: 'null' - type: object 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.