Uptime: Wiki

Parameters

Path Parameters

id*integer

Entity id

Formatint64

Range0 <= value

Code example

curl -X GET "https://example.com/api/v1/racks/0"

Response example

{  "id": 0,  "az_id": 0,  "name": "string",  "capacity_u": 0,  "used_u": 0,  "power_budget_w": 0,  "power_draw_w": 0,  "visual": {    "power_pct": 0.1,    "ambient_heat": 0.1  },  "draped_cable_count": 0,  "depth_m": 0.1,  "floor_slot": 0,  "wall_mount": true,  "pending_placement": true,  "held_by": 0,  "held": true,  "resale_dollars": 0.1,  "binding_key": "string"}

Response body

200The entity

application/json

id*integer

Formatint32

Range0 <= value

az_id*integer

Formatint32

Range0 <= value

name*string

capacity_u*integer

Formatint32

Range0 <= value

used_u?integer

U slots actually consumed in this rack, counting EVERY rack occupant: hosts, switches, patch panels, security appliances, EDDs and gateways. Same population as Engine::occupied_u, sourced from the one-pass Engine::occupied_u_by_rack.

Added in PROTOCOL 49 (UG-294). Clients previously re-summed u_size over the hosts array, which under-reported by everything racked that was not a server, and could only be right at world scope where the fleet-wide capacity block already answered it. Do not re-derive this client-side; a second copy of the occupant list is what drifted.

Formatint32

Range0 <= value

power_budget_w*integer

Formatint32

Range0 <= value

power_draw_w*integer

Formatint32

Range0 <= value

visual*

draped_cable_count?integer

Cables touching this rack that have no managed routing path. Renderer can paint the rack's "neatness" badge from this.

Formatint32

Range0 <= value

depth_m?number

Internal depth in metres. Drives the chassis-fit check at switch placement (SwitchSku::chassis_depth_m()) and lets the rack inspector show "this is a 450 mm wall-mount cabinet, the 700 mm spine you ordered won't fit." Resolved engine-side via Rack::depth_m(), so legacy saves get the standard-DC fallback.

Formatfloat

floor_slot?|

Index into the AZ's rack-slot grid where this rack physically stands. Renderer looks up RackSlot{N} Marker3D anchors under the world scene to place it. None for tiers that use authored aisle layouts instead of the slot grid.

Formatint32

Range0 <= value

wall_mount?boolean

True for the wall-mounted cabinet that ships as a fixture of the Garage / SmallColo rooms. Renderer binds the authored WallRack node to this rack's id (no procedural visual) and the inspector surfaces AZ-level edd + floor-tower context above / below the U stack.

pending_placement?boolean

True while this rack is a bought-but-not-installed crate in the shipping zone. The renderer draws a crate prop (not a rack chassis) and the player carries it to a floor slot via InstallRack.

held_by?integer

MULTIPLAYER — which player is carrying this crate. Meaningless unless held is true. Only meaningful while pending_placement is true.

The renderer skips a held crate's shipping-zone prop and excludes it from the pile layout, so both clients agree about which crates are on the floor and where. Before this, each client hid only the crate IT was carrying, and the pile is indexed by position in the remaining list — so two players carrying crates saw two different piles.

Session state: load_reported clears it, so this is always 0 on the first snapshot after a load.

Formatint32

Range0 <= value

held?boolean

Is anybody carrying it? Separate from held_by because PlayerId::LOCAL is 0 (see DeliveryView::held).

resale_dollars?number

Resale value if the rack is uninstalled and sold at the sell zone. Surfaced so the carry HUD can show "Sell for $X".

Formatdouble

binding_key?|

Symbolic key tying this rack to an authored scene node of the same name. When set, world_equipment_sync binds node.name == binding_key and stamps the node's entity_id — the multi-rack generalization of the single-wall-rack first-by-kind matcher. None for player-bought / procedurally-spawned racks.

Rack

Parameters

Try the endpoint

Code example

Response example

Response body

On this page