Retrieving a Universal Record with a Known Locator

If the Universal Record locator code is known, a Universal Record can be retrieved by using the Universal Record Retrieve request. Whenever possible, any PNR data stored in the Universal Record is validated against the PNR data in the provider's system.

Notes:

Schema

See the following transactions for Retrieving a Universal Record:

Request

Note: Universal API supports retrieval of group bookings. This is limited functionality. This functionality is controlled by a PCC switch. Please contact your Travelport representative or open an Incident Report to activate this enhancement.

  1. Send UniversalRecordRetrieveReq with the following minimum information:.
    • Credentials required for access. To retrieve a Universal Record, the UserID in the Credentials must match the credentials used to create the Universal Record or be an ID that has branch access to the original ID.

    • A valid @UniversalRecordLocatorCode.

  2. Enter @TravelerLastName and ProviderReservation @ProviderCode and @ProviderLocatorCode to retrieve a PNR and use the traveler last name for validation.

  3. Notes: @TravelerLastName is an attribute of UniversalRecordRetrieveReq.

  4. Enter @ViewOnlyInd to view a PNR in Universal Record format without saving it as a Universal Record.

  5. Enter @RetrieveProviderReservationDetails to display provider details.

  6. Optionally, set @ReturnUnmaskedData="true" Release 20.3
  7. Optionally, set @ReturnAmenities="true" to return Routehappy content. N

Response

During the retrieval process, Universal API synchronizes any PNR data in the Universal Record with the available data from the respective providers' latest versions of the PNR. However, Universal API's ability to update a given Universal Record and associated PNRs is dependent on the provider's or supplier's support of this functionality. Suppliers such as Low Cost Carriers in ACH and rail providers in RCS do not typically support strong modify functionality, and may synchronize only a limited amount of the PNR data.

UniversalRecordRetrieveRsp returns the requested Universal Record (UR) and synchronizes data in the UR with the provider PNR.

Troubleshooting

If you receive the error No provider reservation to import when trying to retrieve or import a PNR that does have a segment, it means that the segment is in a non-standard format that Universal API does not recognize. You can force the import/retrieve of the PNR by adding a retention segment in a format that Universal API recognizes (such as a TVL segment).

Exceptions