✨ Document the read-only Booking Cancelation Protection Summaries resource — the per-booking summary of cancelation-protection amounts (commissionable amount, eligible protection amount, rent revenue, policy, and churned_at) used for accounting reconciliation. Listing and fetching require the new bookings_cancelation_protection_readOAuth scope, which grants read access to this data.
📚 Document the per-application connected-accounts cap on private applications. Private apps are limited to 5 connected accounts by default; new installations (both OAuth and private access code) are blocked once the cap is reached. Partners can contact partners@smily.com to formalize the partnership and lift the cap.
✨ 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.
📚 Document how the channel attribute on an Inbox Message controls relay to the originating platform (Airbnb, Booking.com, etc.) and how to derive the right value from the Conversation's default_channel. See the Inbox Messaging guide.
📚 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.
✨ 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.
🐞 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.
✨ Document the difference between map and map_with_price_variation on the Mid Term Rate Map endpoint, and how the per-day price modifier is resolved from Applications Periods Rentals and the Application's default_price_increase.
