Linking Universal Records
Two or more Universal Records can be linked to each other if the records have a business relationship, such as travelers or travel groups in separate records who are traveling together.
-
Linkage is bi-directional: If UR A is linked to UR B, then UR B is linked to UR A.
-
Linkage can be applied to all Universal Records in the same Agency Branch.
-
Archived Universal Records cannot be linked.
Adding Universal Record Links
The optional LinkedUniversalRecord element can be used to add linking during the following functions:
-
Creating reservations for the following segment types:
-
Air reservations AirCreateReservationReq
-
Hotel reservations HotelCreateReservationReq
-
Vehicle reservations VehicleCreateReservationReq
-
Rail reservations RailCreateReservationReq
-
Passive segments PassiveCreateReservationReq
-
Requesting a Universal Record History
LinkedUniversalRecord can contain one or more child UniversalLocatorCode element to identify each Universal Record that is linked to the current Universal Record. A Key for each Locator Code uniquely identifies each link created between Universal Records.
The LinkedUniversalRecord element is then returned in the corresponding response for each function, and is added to the Universal Record data.
Modifying Universal Record Links
When modifying a Universal Record:
-
UniversalRecordAdd/LinkedUniversalRecord is used to add a link to an existing record.
-
UniversalRecordDelete with an Element value set 'LinkUniversalRecord' is used to delete a link. The Key for the specific link is also required.
Error Responses
An error response is returned if a request is made to:
-
Duplicate an existing link.
-
Link archived Universal Records.
-
Link Universal Records from different Agency Branches.
-
Link invalid Universal Records (e.g., URs that are not found within Universal API or have invalid Record Locators).