---
title: "Create Expected Rack"
method: POST
path: "/v2/org/{org}/nico/expected-rack"
tags: ["Expected Rack"]
---

# Create Expected Rack

`POST /v2/org/{org}/nico/expected-rack`

Create an Expected Rack to pre-register a rack expected to be discovered at a Site. The `rackId` is an operator-supplied string identifier (not a UUID) that uniquely identifies the rack within the Site.

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

Alternatively, Tenant Admins with `TargetedInstanceCreation` capability can also create Expected Racks if they have an account with the Site's Infrastructure Provider.

Chassis identity and physical location information are conveyed via well-known label keys in `labels`:
- `chassis.manufacturer`, `chassis.serial-number`, `chassis.model`
- `location.region`, `location.datacenter`, `location.room`, `location.position`

## Request body

- ExpectedRackCreateRequest — Request data to create a new Expected Rack. The `rackId` is an operator-supplied string identifier (not a UUID) that must be unique within the Site. Chassis identity and physical location information are conveyed via well-known label keys in `labels`: - `chassis.manufacturer`, `chassis.serial-number`, `chassis.model` - `location.region`, `location.datacenter`, `location.room`, `location.position`
  - `siteId` string, uuid, required — ID of the Site the Expected Rack belongs to
  - `rackId` string, required — Operator-supplied identifier for the rack (string, not UUID). Must be non-empty and unique within the Site.
  - `rackProfileId` string, required — Identifier of the Rack Profile this rack conforms to. Must be non-empty.
  - `name` string, nullable — Human-readable name of the Expected Rack
  - `description` string, nullable — Human-readable description of the Expected Rack
  - `labels` Labels

## Response `201`

Created

- ExpectedRack — An Expected Rack represents a rack that is expected to be discovered at a Site. The `rackId` is an operator-supplied string identifier (not a UUID) that uniquely identifies the rack within the Site. Each Expected Rack references a Rack Profile that describes the rack's expected layout and capabilities. Chassis identity and physical location information are conveyed via well-known label keys in `labels`: - `chassis.manufacturer`, `chassis.serial-number`, `chassis.model` - `location.region`, `location.datacenter`, `location.room`, `location.position`
  - `id` string, uuid — Unique identifier (UUID) for the Expected Rack
  - `rackId` string — Operator-supplied identifier for the rack (string, not UUID). Unique within a Site.
  - `siteId` string, uuid — ID of the Site the Expected Rack belongs to
  - `rackProfileId` string — Identifier of the Rack Profile this rack conforms to
  - `name` string — Human-readable name of the Expected Rack
  - `description` string — Human-readable description of the Expected Rack
  - `labels` Labels
  - `created` string, date-time — ISO 8601 datetime when the Expected Rack was created
  - `updated` string, date-time — ISO 8601 datetime when the Expected Rack was last updated

## 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

---

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