Retrieve Itinerary

 

Once a PNR has been created on the Sabre Host, this Web Service offers capabilities allowing Airline or Agency to retrieve PNR data using PNR Locator as a search criterion. It also enables retrieving PNR from AAA session. Request payload can be further specified by using "ReturnOptions" which determine response message content.

API Information

Target Audience
All Sabre APIs Customers
Current Version
1.18.0
Authentication
Session or Sessionless Token
Service Action Code
getReservationRQ

For Read Only Access use the Trip option as the PNR is not unpacked into the user AAA Session. The PNR Locator must always be specified in the request.

For Update Access use the Stateful option as this will unpack the PNR into the user AAA session and be available for follow up Sabre entries. If a Locator is specified in the request the service checks the Locator in the AAA and if they match retrieves the current data in the AAA, if they do not match the service will unpack the PNR into the AAA session as long as the current session is available and there are no updates outstanding.

Sample Request

<GetReservationRQ Version="1.18.0" xmlns="http://webservices.sabre.com/pnrbuilder/v1_18">
	<Locator>ZNDNPC</Locator>
	<RequestType>Stateful</RequestType>
	<ReturnOptions>
		<ViewName>VaDefaultWithPq</ViewName>
		<ResponseFormat>STL</ResponseFormat>
	</ReturnOptions>
</GetReservationRQ>

Sample Response

<stl18:GetReservationRS Version="1.18.0" xmlns:stl18="http://webservices.sabre.com/pnrbuilder/v1_18" xmlns:ns6="http://services.sabre.com/res/orr/v0" xmlns:raw="http://tds.sabre.com/itinerary" xmlns:ns4="http://webservices.sabre.com/pnrconn/ReaccSearch" xmlns:or112="http://services.sabre.com/res/or/v1_12">
	<stl18:Reservation numberInParty="1" numberOfInfants="0" NumberInSegment="1">
		<stl18:BookingDetails>
			<stl18:RecordLocator>ZNDNPC</stl18:RecordLocator>
			<stl18:CreationTimestamp>2018-03-02T04:49:00</stl18:CreationTimestamp>
			<stl18:SystemCreationTimestamp>2018-03-02T04:49:00</stl18:SystemCreationTimestamp>
			<stl18:CreationAgentID>VLZ</stl18:CreationAgentID>
			<stl18:UpdateTimestamp>2018-03-02T04:49:07</stl18:UpdateTimestamp>
			<stl18:PNRSequence>1</stl18:PNRSequence>
			<stl18:DivideSplitDetails/>
			<stl18:EstimatedPurgeTimestamp>2018-04-13T00:00:00</stl18:EstimatedPurgeTimestamp>
			<stl18:UpdateToken>-7c81a901f8f94089e5c21b787fec0b24f26e0b017645c70b</stl18:UpdateToken>
		</stl18:BookingDetails>
		<stl18:POS AirExtras="false" InhibitCode="U">
			<stl18:Source BookingSource="W0H3" AgentSine="VLZ" PseudoCityCode="W0H3" ISOCountry="US" AgentDutyCode="*" AirlineVendorID="AA" HomePseudoCityCode="HDQ"/>
		</stl18:POS>
		<stl18:PassengerReservation>
			<stl18:Passengers>
				<stl18:Passenger id="4" nameType="S" nameId="01.01" nameAssocId="1" elementId="pnr-4.1">
					<stl18:LastName>GENERALNY</stl18:LastName>
					<stl18:FirstName>ANDZEJ</stl18:FirstName>
					<stl18:Seats/>
				</stl18:Passenger>
			</stl18:Passengers>
			<stl18:Segments>
				<stl18:Segment sequence="1" id="3">
					<stl18:General isPast="false" dayOfWeekInd="5">
						<stl18:Line Number="1" Type="ATX" Status="GK"/>
						<stl18:Vendor Code="LS"/>
						<stl18:NumberInParty>1</stl18:NumberInParty>
						<stl18:OriginLocation LocationCode="DFW"/>
						<stl18:DestinationLocation LocationCode="ORD"/>
						<stl18:DateTime>2018-04-13T00:00:00</stl18:DateTime>
						<stl18:Text/>
					</stl18:General>
				</stl18:Segment>
			</stl18:Segments>
			<stl18:TicketingInfo/>
			<stl18:ItineraryPricing/>
		</stl18:PassengerReservation>
		<stl18:ReceivedFrom>
			<stl18:Name>ZAMOJ</stl18:Name>
		</stl18:ReceivedFrom>
		<stl18:PhoneNumbers>
			<stl18:PhoneNumber id="5" index="1" elementId="pnr-5">
				<stl18:CityCode>SAT</stl18:CityCode>
				<stl18:Number>7373736645-H</stl18:Number>
			</stl18:PhoneNumber>
		</stl18:PhoneNumbers>
		<stl18:EmailAddresses/>
	</stl18:Reservation>
</stl18:GetReservationRS>

If you are a Sabre customer currently using Sabre APIs in production, access  Resources  

Docs Navigation