---
title: "Decommission a Machine"
method: POST
path: "/v2/org/{org}/nico/machine/{machineId}/decommission"
tags: ["Machine"]
---

# Decommission a Machine

`POST /v2/org/{org}/nico/machine/{machineId}/decommission`

Start decommissioning a Machine. The Machine must be in Core's `Ready`
state, and every attached DPU must support BFB installation through
Redfish. The operation is asynchronous; use the Machine status to
observe workflow progress.

Org must have an Infrastructure Provider entity and own the Site that
the Machine belongs to. User must have authorization role with
`PROVIDER_ADMIN` suffix.

## Response `202`

Machine decommissioning was accepted and will proceed asynchronously.

- MessageResponse — Structured response with a human-readable message
  - `message` string, required — Human-readable outcome of the request

## Other responses

- `400` — Error response when request data cannot be validated
- `403` — Error response when user is not authorized to call an endpoint or retrieve/modify objects
- `404` — Error response when requested object is not found
- `412` — The Machine cannot be decommissioned in its current Core state or its DPUs do not support the required BFB installation.
- `500` — Response when the API handler encounters an unexpected error
- `503` — Core is unavailable.
- `504` — The Core proxy request timed out.

## Changes

- **2026-08-21** `5c6bffda4e24` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/nvidia/apis/nvidia-infra-controller-rest-api/changes/v2/org/:org/nico/machine/:machineId/decommission/post.md)

---

[API](https://skmtc.dev/nvidia/apis/nvidia-infra-controller-rest-api.md) · [All operations](https://skmtc.dev/nvidia/apis/nvidia-infra-controller-rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/nvidia/nvidia-infra-controller-rest-api/revisions/a2dc05bef3c1/schema)