Skip to main content
POST
Stop a reservation and release its machines
In the console this is Stop reservation, or Stop VM for Spot. See How spot ends for Spot credits.

Authorizations

Authorization
string
header
required

Create an organization API key in Account Settings > Developer. Do not send this key to the Kubernetes API server.

Path Parameters

reservationId
string<uuid>
required

Reservation ID.

Response

The reservation has ended and its machines are released.

reservationId
string<uuid>
required
status
enum<string>
required
Available options:
confirmed,
active,
completed,
cancelled
isSpot
boolean
required
reservedNodeCount
integer
required
reservedGpuCount
integer
required
startsAt
string<date-time>
required
endsAt
string<date-time> | null
required
customerId
string<uuid>
listingId
string<uuid>
listingTermId
string<uuid>
provisioningType
enum<string>
Available options:
virtual-machine,
bare-metal,
kubernetes,
slurm
facilityId
string<uuid>
gpuSlug
string
gpusPerNode
integer
pricePerGpuHourMicroUsd
integer<int64>

Your agreed reservation rate in integer micro-USD per GPU-hour, including any fee you pay. Historical reservations without a saved rate show the linked listing term price.

durationHours
number | null

Original agreed duration in hours, separate from operational start and end dates. Renewable reservations retain this duration with a null end date. Null when no duration was agreed.

renewable
boolean | null

Whether the reservation contract permits renewal.

downPaymentCents
integer<int64> | null
pendingOperation
string | null
pendingOperationId
string<uuid>
vmDiskId
string<uuid> | null
deployedAt
string<date-time> | null
endReason
string | null
transactionId
string<uuid>
createdAt
string<date-time>
updatedAt
string<date-time>
relistableNodeCount
integer
relistUnavailableReason
string | null
relistableNodeIds
string<uuid>[]