Skip to main content
The OTA_HotelResModifyRS is the response to a modification request for an existing hotel reservation. It confirms whether the requested change was accepted (minor vs. major), returns updated monetary totals when recalculation occurs, and may offer optional extras or upgrade options.

Purpose

This message is used to:
  • Acknowledge minor changes (e.g., comments, non–lead-pax name, contact details) without price recalculation.
  • Return updated totals for major changes (e.g., room/board change) when recalculation is required.
  • Provide status of the modification (<Success/> or <Errors>), and optionally expose Extras and Upgrades in TPA_Extensions.

Structure – Root Element

Key Attributes
  • Version: OTA message version (e.g., 2017.2).
  • EchoToken: Echoes the request token for pairing.
  • TimeStamp: Response generation time (ISO 8601 UTC).
  • xmlns: http://www.opentravel.org/OTA/2003/05.

Structure – Core Elements

Errors

Returned when the modification is rejected. Example rejection:
  • Booking not changed - data received differs from stored data.

HotelResModify

Container for the modified booking state.
The attributes are ISO 8601 timestamps for creation and the last update of the reservation record.

Further Components

The rest of the response follows the same structure as a OTA_HotelResRS

Complete Example

Best Practices

  • If a connected PMS/Channel Manager does not support modifications, the system returns an error; execute cancel & rebook under the same Distributor reference with a new Child reference.
  • Hotel changes (switching to a different property) require cancel & rebook.
  • Adding rooms: send a new OTA_HotelResRQ with the same Distributor reference and a new Child reference; no modify needed.
  • On every modify cycle: ReadRQModifyRQ (Quote) → review response → ModifyRQ (Commit).
  • Use RateOverrideIndicator to detect whether recalculation occurred at room and booking levels.