Skip to main content

Version 4.12.0

  • ✨ Expose payment_charge_commission on the Bookings endpoint — the Payment Charge commission amount — the commission charged by an OTA for processing payments (e.g. Payments by Booking.com). Available on the bookings_write_owned, bookings_read, and bookings_write scopes.
  • 📚 Document the accuracy caveat: when the payout has not yet been reconciled from Booking.com via Smily Pay, the value may be off by approximately one cent — the real amount is only known once the payout is reconciled.

Version 4.11.0

  • 📚 Document that start_at and end_at on Create a new booking must be full datetimes whose time-of-day matches the rental's checkin_time / checkout_time. Date-only values get coerced to midnight and trip the "is within a used period" validation against adjacent bookings. The booking-creation example payloads now use full datetimes instead of START_AT / END_AT placeholders.

Version 4.9.0

  • ✨ Expose start_at_global and end_at_global on the Booking resource. These are the booking's check-in and check-out as true UTC instants (rental's timezone applied), suitable for absolute time-window comparisons. The existing start_at and end_at remain wall-clock values in the rental's local timezone.

Version 4.8.0

  • 🐞 Webhook deliveries now respect each application's per-account rental exposure (whitelist / blacklist) configuration, mirroring the visibility of GET /rentals. Rental-scoped events (booking_*, inquiry_*, photo_*, payment_*, review_*, etc.) are only delivered for rentals exposed to the receiving application. See Webhook subscriptions → Rental access scope.

Version 4.5.0

  • ✨ Document the application lock behavior when setting nightly_rates_managed_externally to true on a Rental: rates management is locked to the calling application, and a different application attempting to update the Nightly Rate Map will receive an explicit error.