Reservations
Get reservation details (optional, for debugging)
Retrieve current status and details of a reservation by ID. Useful for debugging and monitoring long-running operations. EXPIRY (NORMATIVE, revision 2026-07-03):
- If the reservation exists but its status is EXPIRED, the server MUST return 410 with error=RESERVATION_EXPIRED (this operation's declared 410 response). A reservation that never existed returns 404 NOT_FOUND.
- EXPIRED reservations remain discoverable via listReservations, which returns them as normal 200 rows with status=EXPIRED — the 410 applies only to this single-resource GET. This codifies the reference implementation's settled behavior; the pre-revision text enumerated only commit/release/extend in the 410 rule, leaving GET ambiguous.
TENANCY (NORMATIVE):
- Under ApiKeyAuth: if the reservation exists but is owned by a different effective tenant, the server MUST return 403 FORBIDDEN.
- Under AdminKeyAuth (added 2026-04-13): admin operators can read any reservation regardless of owning tenant; reservation_id already pins the owner so no extra parameter is needed.
get/v1/reservations/{reservation_id}
Request
- Base URL: https://api.cycles.local
- URL: https://api.cycles.local/v1/reservations/{reservation_id}
- Auth: one of:
- API key in header X-Cycles-API-Key
- API key in header X-Admin-API-Key
Path parameters
reservation_idstring required
Response
Reservation details
Example response
{
"reserved": {
"unit": "USD_MICROCENTS",
"amount": 500000
},
"committed": {
"unit": "USD_MICROCENTS",
"amount": 500000
}
}Changes
No recorded changes to this operation across all 1 revision of this API.