We've made four new improvements to how reservations, webhooks and the Public API handle cancellations and no-shows. These are now available to all API customers.
1) Richer reservation.updated Webhooks (Booking.com)
The reservation.updated event now fires when:
The Booking.com cancellation fee is set or changed (what the host keeps after guest cancellation).
A Booking.com no-show is reported, indicating whether the fee was waived.
Two new fields are available on the Public API reservation: bookingcomNoShowReportedAt and bookingcomNoShowFeeWaived. Webhook subscribers receive these updates automatically without polling.
2) Accurate Cancellation Policy Details in the Public API
Reservation-specific cancellation policies are now delivered consistently via cancellationPolicyDetails. Fixed issues include:
Resolved incorrect refund amounts on non-refundable Booking.com rates.
Fixed time boundary overlaps on arrival-day refund tiers.
3) Report Booking.com No-Shows via the Public API
You can now programmatically report Booking.com no-shows instead of using the dashboard.
PUT /v1/reservations/{reservationId}/statuses/noShow (supports the waive-fee flag). This pairs with the webhook updates for a complete read and write no-show automation flow.4) Clearer "Cancel Reservation" UI Action
The Cancel reservation button on the reservation page now has improved visibility:
Always visible to users with cancellation permissions.
Disabled with an explanatory tooltip if the channel does not support cancellation, clarifying why the action is unavailable.
These updates give you complete, automated control over cancellation policies and Booking.com no-show workflows directly through the API, reducing manual work and improving data accuracy across your connected channels.
For more details, you can check out our Hostaway API documentation.