Reservation endpoints previously returned addon data from the current hotel configuration rather than from the addon details at the time of booking. This meant that if an addon price was updated after a reservation was created, the API would return the updated price rather than the original price applied at the time of booking.

Addon data returned by reservation endpoints now correctly reflects the addon details recorded at the time of booking, regardless of any subsequent configuration changes.