The Kong Hotels Guest Stay API covers what happens after a booking is made: online check-in, room readiness, mobile keys, in-stay service requests and express check-out. It powers the Kong Hotels app and is open to partners who run guest messaging, concierge or corporate travel tools.
How it fits with the Partner API
| Need | Use |
|---|---|
| Content, availability, pricing, booking, cancellation, add-ons, folio | Kong Hotels Partner API |
| Check-in, room status, mobile keys, service requests, check-out | Guest Stay API (this one) |
Both APIs share identifiers. A stay is addressed by the reservation’s confirmationNumber, and properties by the same propertyCode. Nothing here creates, changes or prices a reservation.
Stay lifecycle
pre_arrival ──POST /check-in──▶ checked_in ──POST /check-out──▶ checked_out
│
├─ POST /keys (once room is ready)
├─ POST /service-requests
└─ POST /late-check-out
Each stay returns an actions object saying which of these are allowed right now. Calling one that isn’t allowed returns 409.
Authentication
Same as the Partner API: Kong Gateway validates your API key and forwards your consumer identity. You can only see stays for reservations your consumer created.
Conventions
Responses wrap payloads in data, lists use cursor pagination, errors use RFC 9457 problem details, and writes accept an optional Idempotency-Key. All of this matches the Partner API.
- Server 1:https://stay.konghotels.cloud
Production (Kong Gateway)
KongKeyAuth (apiKey)
Your API key, validated by Kong Gateway.