Current limits
What the Channel API does not cover today, and what to agree with OnSeason instead.
These parts of a distribution partnership are outside the API today. Plan for them in your integration and in your agreement with OnSeason.
Payments and merchant of record
A reservation doesn't take a card number, a payment token, or any other payment instrument. The API records prices, the optional commission, and the cancellation charge, but it doesn't charge the guest, refund them, or settle with you.
Who is the merchant of record, how the guest pays, and how commission, deposits, refunds, invoicing, and settlement work are set in your commercial agreement with OnSeason.
Webhooks
There are no partner webhooks yet. Don't depend on events such as booking.confirmed, booking.cancelled, booking.modified, or availability.changed. To follow a booking after you create it, get the reservation.
Reservation lists
Channel keys can read reservations one at a time by ID. There is no endpoint to list or search your reservations, so keep the booking map on your side.
Idempotency
Reservation creation is not idempotent. See Never retry a reservation blindly.
Rate limits
OnSeason doesn't publish a fixed rate limit or a Retry-After contract yet. Agree expected volumes and load tests before launch.
Booking changes
The API books and cancels. It doesn't change dates, guests, or price on an existing reservation. To change a booking, cancel it and book again, after you agree with the guest how the cancellation terms apply.