---
title: "Power control NVLink Domains"
method: PATCH
path: "/v2/org/{org}/nico/domain/nvlink/power"
tags: ["NVLink Domain"]
---

# Power control NVLink Domains

`PATCH /v2/org/{org}/nico/domain/nvlink/power`

Power control one or more NVLink Domains identified by UUID. Flow resolves each NVLink Domain to its member Racks and creates one task per Rack.

Supported power states: `on`, `off`, `cycle`, `forceoff`, `forcecycle`.

Org must have an Infrastructure Provider entity. User must have authorization role with `PROVIDER_ADMIN` suffix.

## Request body

- BatchUpdateNVLinkDomainPowerStateRequest — Request body for power control of explicitly selected NVLink Domains
  - `siteId` string, uuid, required — ID of the Site
  - `domainIds` string[], required — UUIDs of the NVLink Domains to power control. IDs must be unique after UUID normalization (case-insensitive).
  - `state` 'on' | 'off' | 'cycle' | 'forceoff' | 'forcecycle', required — Target power state
  - `ruleId` string, uuid — Optional Operation Rule UUID. When set, pins every task spawned by this operation to the named rule and overrides Flow's default rule resolution.
  - `overrideReadinessCheck` boolean — When true, proceed even if one or more target components (or hosts on the owning rack for rack-scoped components) are reported as not ready by their persisted status. Intended for operator-supervised maintenance.

## Response `200`

OK

- UpdatePowerStateResponse — Response for power control operations containing task IDs for tracking
  - `taskIds` string[] — List of task IDs created for the power control operation (one per rack)

## 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
- `500` — Response when the API handler encounters an unexpected error
- `503` — Response when the API handler encounters an unexpected error
- `504` — The Site did not return a result within the request budget allocated to Site communication within the request cycle. This can occur if the Site Controller is down or under heavy request load. Operations are in general safe to retry. In rare cases, operations that create or update resources may succeed even if timeout is returned.

## Changes

- **2026-08-27** `59eeccfdaa6f` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/nvidia/apis/nvidia-infra-controller-rest-api/changes/v2/org/:org/nico/domain/nvlink/power/patch.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/2d6cc0ee8a4a/schema)