---
title: "Release GPU units to the spot market (double sell)"
method: POST
path: "/v1/nodes/{nodeId}/reservations/{id}/release"
tags: ["Reservations"]
---

# Release GPU units to the spot market (double sell)

`POST /v1/nodes/{nodeId}/reservations/{id}/release`

The double-sell operation. The named units stay part of the reservation but go on the market: anyone may buy them, at tier=spot and only at tier=spot, which is what makes them terminable by the capacity owner at any time. An ordinary community or verified request will never be placed on them, so released capacity can always be reclaimed. Callable by a platform operator, the org that owns the node, or an org in the reservation's managingOrgIds.

## Path parameters

- `nodeId` string, required
- `id` string, required

## Request body

- ReservationUnitsRequest
  - `reason` string — Recorded in the audit trail.
  - `unitIds` string[], required

## Response `200`

OK

- NodeReservation — Exclusive placement rights for a set of orgs over specific GPU units of one node, for a term. Scoped to units, not GPU counts, because units are the indivisible allocation primitive.
  - `allowedOrgIds` string[], required — The audience: orgs that may place workloads on the reserved units.
  - `contractRef` string
  - `createdAt` string
  - `endsAt` string — Absent = open-ended until cancelled
  - `id` string, required
  - `managingOrgIds` string[] — Orgs that may release these units to the market, reclaim them, and terminate the spot workloads on them, on the node owner's behalf. Being in the audience does not confer this.
  - `nodeId` string, required
  - `reason` string
  - `releasedUnitIds` string[] — The subset of reservedUnitIds currently on the spot market (double sell). Still this reservation's capacity, sellable to anyone at tier=spot only, and reclaimable at any time.
  - `reservedUnitIds` string[], required
  - `skipped` string[] — Reclaim only: VM ids left running because they are not spot.
  - `startsAt` string, required
  - `status` 'pending' | 'active' | 'expired' | 'cancelled' | 'needs-review', required — needs-review means the node's GPU topology changed under the reservation: it grants nothing (and withholds its units from everyone) until an operator re-affirms it.
  - `terminated` string[] — Reclaim only: spot VM ids terminated to free the reclaimed units.
  - `topologyGen` integer — Node topology generation this reservation was written against
  - `updatedAt` string
  - `wouldSkip` string[] — Reclaim dry run only: VM ids that would be left running.
  - `wouldTerminate` string[] — Reclaim dry run only: the spot VM ids this call would terminate.

## Other responses

- `400` — The request is invalid
- `401` — Missing or invalid API key
- `403` — API key lacks the required scope
- `404` — Resource not found
- `409` — The request conflicts with existing state

---

[API](https://skmtc.net/openrelay/apis/openrelay-api.md) · [All operations](https://skmtc.net/openrelay/apis/openrelay-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/openrelay/openrelay-api/revisions/138b4ef69d2f/schema)