Reservation endpoints were returning addon data from the hotel’s current configuration rather than from the addon details at the time of booking, in cases where the addon is linked to a rate. This meant that changes to addon inclusion settings made after a booking was created were incorrectly reflected in the API response.

Reservation endpoints now correctly return addon details as they were recorded at the time of booking, regardless of subsequent configuration changes.