Retrieving Saved Trips

Saved trips that have not been archived can be retrieved using a saved trip Locator Code. 

Notes:

• Saved trips that are archived are not retrievable.
• Saved trips that are not associated to a Universal Record are purged (deleted) 24 hours after the last dated segment in the Saved Trip is past date.

Schema

Located in Universal.xsd:

• SavedTripRetrieveReq
• SavedTripRetrieveRsp

How To

1. Enter the @LocatorCode of the saved trip in the SavedTripRetrieveReq .

2. Enter the @TravelerLastName for the saved trip.

3. The response is returned in SavedTripRetrieveRsp.

When a Saved Trip that is associated to a Universal Record (UR) is retrieved, Universal API checks whether the last past-dated segment in the Saved Trip is 72 hours past date. If yes:

• Universal API changes the status of the Saved Trip from Active to Archivedand returns a message in SavedTripRetrieveRsp: Saved Trip has been archived.

When a Saved Trip that is not associated to a UR is retrieved, Universal API checks whether the last past-dated segment in the Saved Trip is 24 hours past date. If yes:

• Universal API purges (deletes) the Saved Trip and returns a warning in SavedTripRetrieveRsp: Unable to retrieve Saved Trip.

When a Universal Record (UR) that is associated to a Saved Trip is retrieved, Universal API checks if the last past dated segment in the UR is 72 hours past date. If the last past dated segment in the UR is 72 hours or more past date:

• Universal API changes the status of the UR from Active to Archived and returns an error message in UniversalRecordRetrieveRsp.

• The associated Saved Trip is retrieved when the status of the UR is changed. If the Saved Trip has a status of Active, the status is changed to Archived regardless of whether the Saved Trip is past date.