UniversalRecordModifyReq
UniversalRecordModifyRsp
UniversalRecordModifyReq/UniversalModifyCmd/RailUpdate
Currently, the only modification supported for booked Rail segments is an update of the Booking Action, which is currently available only for SNCF (2C).
Please Note: Other updates, including station locations, dates, and times, cannot currently be modified through Travelport Universal API™. The supplier (distributor) must be contacted directly for these types of updates.
Updating Rail Segments
Request
UniversalRecordModifyReq/UniversalModifyCmd/RailUpdate
BookingAction
To modify an existing Rail reservation, the Universal Record (UR) that contains the PNR (RCS booking record) must first be retrieved using UniversalRecordRetrieveReq. The retrieved Universal Record can then be modified.
Currently the only update supported for rail reservation is a modification to the Booking Action (BookingAction). SNCF (2C) is currently the only Universal API rail supplier that supports updates to an existing rail reservation.
Note that BookingAction Type="Initiate" cannot be set via Rail Update because it applies only to new bookings and not to existing booking. The Booking Action Type can be modified from Initiate or Final to Ticket or FinalTicket by adding Form of Payment and Payment information.
The required ReservationLocatorCode attribute identifies the provider’s PNR booking record to which the rail segment is added. This ReservationLocatorCode is assigned by the provider (RCS) and is distinct from the identifier for the Universal Record locator that is issued by Universal API.
Response
UniversalRecordModifyRsp/UniversalRecord/RailReservation
@BookingStatus is mandatory but the string value is not validated. Common values are: Final, Ticketed, Initiate, Exchanged, Cancel, Refunded, and Unknown.
There can be only one @BookingStatus value per booking. If there are multiple train segments in the booking, they must all have the same value.
