Availability flow

The normal sequence is:

1. POST /api/v1/booking/availability/search
2. POST /api/v1/booking/quote
3. POST /api/v1/booking/reservations

Minimal request model

Always send:

• hotel id
• check-in date
• check-out date
• adult count

Optional fields can include children, room count and selected services.

Reservation changes

After creation you can:

• modify via PATCH /api/v1/booking/reservations/{reservation}
• cancel via POST /api/v1/booking/reservations/{reservation}/cancel

Error handling

Plan for:

• validation errors
• no availability
• restriction windows
• payment or checkout issues if you trigger commercial flows

Use the OpenAPI reference for examples and current response payloads.