GUguesty
Channel Commission

[Beta] Update reservation channel commission

Changed on

[Beta] Sets a custom channel commission amount on a reservation and updates the folio.

Send the new amount in the reservation currency and realizationDates for when it should be recognized.

Realization-date rules:

  • Dates are evaluated in the listing timezone.
  • The allowed recognition window is the inclusive from/to range returned by Guesty Accounting™ for this reservation’s channel-commission (CM) line item (allowedRanges[0]). It is reservation-specific (driven by the account’s accounting / business-model recognition rules). This API does not return the window; a date or both ends of a from/to range (after normalization) must fall inside it, or the request returns 400 (realization date not in allowed dates range).
  • For from/to, the range must also match the stay: before or on check-in use check-in→checkout; during the stay use today→checkout. There must be enough days left before checkout. The stored end date is normalized to checkout minus one day.

Not allowed when the channel has already deducted the commission from the host payout (a prededucted host channel fee is already on the folio — common for Booking.com). In that case the request returns 400.

put/channel-commissions-v2/reservations/{reservationId}

Request

  • Base URL
    https://open-api.guesty.com/v1
  • URL
    https://open-api.guesty.com/v1/channel-commissions-v2/reservations/{reservationId}
  • Auth
    API key in header authorization

Path parameters

reservationIdstring required
Example:64a1f2c3e4b0a1b2c3d4e5f6

Reservation ID (for example 64a1f2c3e4b0a1b2c3d4e5f6).

Request body

amountnumber required

New channel commission amount in the reservation currency (for example USD or EUR). There is no separate currency field — send the amount already in that currency.

Example request

{
  "realizationDates": {
    "date": "2026-01-01"
  },
  "amount": 100
}

Response

The recalculated reservation folio after the channel commission change. The response body is the full folio; the schema below documents the fields most relevant to this operation (reservationId, currency, hostServiceFee, and related tax fields when present).

reservationIdstring required

Reservation ID

currencystring required

Reservation currency (ISO 4217). All amounts in the response use this currency.

hostServiceFeenumber required

Channel commission amount after the override, in the reservation currency.

hostServiceFeeTaxnumber

Tax on the channel commission, when applicable, in the reservation currency.

hostServiceFeeIncTaxnumber

Channel commission including tax, when applicable, in the reservation currency.

Example response

{
  "reservationId": "64a1f2c3e4b0a1b2c3d4e5f6",
  "currency": "USD",
  "hostServiceFee": 100,
  "hostServiceFeeTax": 10,
  "hostServiceFeeIncTax": 110
}

Changes