PNR Services Web Service Technical Guide
PNR Services Technical
Documentation
CreateReservationRQ (1.11.0) Web Service Guide
April 16, 2015
Version 1.0
PNR Services Web Service Technical Guide
Reference
Prepared for
PNR Services Clients
Prepared by
Sabre Inc.
Date
April 15, 2014
© 2008, Sabre Inc. All rights reserved.
This documentation is the confidential and proprietary intellectual
property of Sabre Inc. Any unauthorized use, reproduction,
preparation of derivative works, performance, or display of this
document, or software represented by this document, without the
express written permission of Sabre Inc. is strictly prohibited.
Sabre, the Sabre logo design, and Product Name are trademarks
and/or service marks of an affiliate of Sabre Inc. All other
trademarks, service marks, and trade names are owned by their
respective companies.
Sabre Inc. Confidential/All Rights Reserved Error! No text of specified style in document. ii
PNR Services Technical User Guide
D O C U M E N T R E V I S I O N I N F O R M A T I O N
The following information is to be included with all versions of the document.
Project Name CreateReservationRQ Project Number 1.11.0
Prepared by Deanna Trussell Date Prepared 16 April 2015
Revised by Date Revised
Revision Reason Revision Control No.
Sabre Inc. Confidential/All Rights Reserved Error! No text of specified style in document. iii
PNR Services Technical User Guide
Table of Contents
P N R S e r v i c e s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i i
T e c h n i c a l U s e r G u i d e . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i i
D O C U M E N T R E V I S I O N I N F O R M A T I O N
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i i
P N R S e r v i c e s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i i i
T e c h n i c a l U s e r G u i d e . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i i i
T a b l e o f C o n t e n t s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i i i
P r o c e s s O v e r v i e w . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1. Introduction................................................................................................................................... 7 1.2. Description ................................................................................................................................... 7 1.3. Views and Subject Areas ............................................................................................................. 9 1.4. New Features introduced in Create Reservation service ........................................................... 10 1.5. Glossary ..................................................................................................................................... 11
R e q u e s t p a r a m e t e r s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 2
2.1 (RQ)Request Type ..................................................................................................................... 12 2.2 (RQ)Return Options ................................................................................................................... 13 2.3 (RQ)POS .................................................................................................................................... 13 2.4 (RQ)Source ................................................................................................................................ 13 2.5 (RQ)Requestor ID ...................................................................................................................... 14 2.6 (RQ)Company Name .................................................................................................................. 15 2.7 (RQ)Arranger Details .................................................................................................................. 15 2.8 (RQ)Person Name ...................................................................................................................... 15 2.9 (RQ)Telephone ........................................................................................................................... 16 2.10 (RQ)Booking Channel ................................................................................................................ 16 2.11 (RQ)TTY Record Locator ........................................................................................................... 16 2.12 (RQ)OAC .................................................................................................................................... 17 2.13 (RQ)New Reservation ................................................................................................................ 17 2.14 (RQ)Itinerary ............................................................................................................................... 17 2.15 (RQ)Product ............................................................................................................................... 17 2.16 (RQ)Product Base ...................................................................................................................... 18 2.17 (RQ)Product Details ................................................................................................................... 18 2.18 (RQ)Hotel ................................................................................................................................... 19
Sabre Inc. Confidential/All Rights Reserved Error! No text of specified style in document. iv
2.19 (RQ)Reservation ........................................................................................................................ 19 2.20 (RQ)Special Prefs ...................................................................................................................... 20 2.21 (RQ)Room Type ......................................................................................................................... 20 2.22 (RQ)Room Rates ........................................................................................................................ 20 2.23 (RQ)Rate Access Code Booked ................................................................................................. 20 2.24 (RQ)Guest Counts ...................................................................................................................... 20 2.25 (RQ)Guarantee ........................................................................................................................... 21 2.26 (RQ)Hotel Total Pricing .............................................................................................................. 21 2.27 (RQ)Total Tax ............................................................................................................................. 21 2.28 (RQ)Total Surcharge .................................................................................................................. 21 2.29 (RQ)Hotel Unique ID .................................................................................................................. 22 2.30 (RQ)Additional Information ......................................................................................................... 22 2.31 (RQ)Address (Hotel) ................................................................................................................... 22 2.32 (RQ)Contact Numbers ................................................................................................................ 22 2.33 (RQ)Commission ........................................................................................................................ 23 2.34 (RQ)Rate Description ................................................................................................................. 23 2.35 (RQ)Hotel Policy ......................................................................................................................... 23 2.36 (RQ)Ground Transportation........................................................................................................ 23 2.37 (RQ)Vendor ................................................................................................................................ 24 2.38 (RQ)Address (Ground Transportation or Rail) ............................................................................ 24 2.39 (RQ)City Codes .......................................................................................................................... 24 2.40 (RQ)State Province Codes ......................................................................................................... 24 2.41 (RQ)Country Codes .................................................................................................................... 25 2.42 (RQ)Service................................................................................................................................ 25 2.43 (RQ)Service Level ...................................................................................................................... 25 2.44 (RQ)Equipment .......................................................................................................................... 25 2.45 (RQ)Service Provider ................................................................................................................. 25 2.46 (RQ)Code ................................................................................................................................... 26 2.47 (RQ)Start Details ........................................................................................................................ 26 2.48 (RQ)Airport Info .......................................................................................................................... 26 2.49 (RQ)Railway Station Info ............................................................................................................ 26 2.50 (RQ)Location Codes ................................................................................................................... 27 2.51 (RQ)Amenities ............................................................................................................................ 27 2.52 (RQ)Stop Details ........................................................................................................................ 27 2.53 (RQ) End Details ........................................................................................................................ 27 2.54 (RQ)External Reservation .......................................................................................................... 27 2.55 (RQ)Restrictions ......................................................................................................................... 28 2.56 (RQ)Agent Loyalty ...................................................................................................................... 28 2.57 (RQ)Passenger .......................................................................................................................... 28 2.58 (RQ)Rate Qualifier ...................................................................................................................... 28 2.59 (RQ)Charges .............................................................................................................................. 29 2.60 (RQ)Charge ................................................................................................................................ 29 2.61 (RQ)Calculation .......................................................................................................................... 29 2.62 (RQ)Rail ..................................................................................................................................... 29 2.63 (RQ)Marketing Carrier ................................................................................................................ 30
Sabre Inc. Confidential/All Rights Reserved Error! No text of specified style in document. v
2.64 (RQ)Operating Carrier ................................................................................................................ 30 2.65 (RQ)Passengers ......................................................................................................................... 30 2.66 (RQ)Supplementary Services ..................................................................................................... 30 2.67 (RQ)Supplementary Service....................................................................................................... 31 2.68 (RQ)Passenger References ....................................................................................................... 31 2.69 (RQ)Train Info ............................................................................................................................ 31 2.70 (RQ)Accommodation .................................................................................................................. 31 2.71 (RQ)Placement ........................................................................................................................... 31 2.72 (RQ)Coach ................................................................................................................................. 32 2.73 (RQ)Rail Fares ........................................................................................................................... 32 2.74 (RQ)Fare .................................................................................................................................... 32 2.75 (RQ)Segment References .......................................................................................................... 33 2.76 (RQ)Fare Description ................................................................................................................. 33 2.77 (RQ)Fees.................................................................................................................................... 33 2.78 (RQ)Document ........................................................................................................................... 33 2.79 (RQ)Form Of Payment ............................................................................................................... 34 2.80 (RQ)Credit Card ......................................................................................................................... 34 2.81 (RQ)Card Holder ........................................................................................................................ 34 2.82 (RQ)File ...................................................................................................................................... 34 2.83 (RQ)Document Rules ................................................................................................................. 34 2.84 (RQ)Transaction Info .................................................................................................................. 35 2.85 (RQ)Person Name (New Reservation) ....................................................................................... 35 2.86 (RQ)Phone Number ................................................................................................................... 35 2.87 (RQ)Profile ................................................................................................................................. 36 2.88 (RQ)Name Association List ........................................................................................................ 36 2.89 (RQ)Ticketing Info ...................................................................................................................... 36 2.90 (RQ)Future Ticketing .................................................................................................................. 36 2.91 (RQ)Ticketing Time Limit ............................................................................................................ 37 2.92 (RQ)Already Ticketed ................................................................................................................. 37 2.93 (RQ)Remark ............................................................................................................................... 37 2.94 (RQ)Segment Association List ................................................................................................... 38 2.95 (RQ)Other Service Information ................................................................................................... 38 2.96 (RQ)Received From ................................................................................................................... 38 2.97 (RQ)Email Address .................................................................................................................... 39 2.98 (RQ)Accounting Line .................................................................................................................. 39 2.99 (RQ)Result Action ...................................................................................................................... 40 2.100 (RQ)Client Context ................................................................................................................. 41
R e q u e s t a n d R e s p o n s e p a y l o a d e x a m p l e s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2
3.1 Sample RQ, RS in CreateReservationsRQ v1.11 ...................................................................... 42 3.1.1 Sample STL, Stateless – add Rail ..................................................................................... 42 3.1.2 Sample STL, Stateless – Tour package ............................................................................ 53 3.1.3 Sample STL, Stateful – add Rail ........................................................................................ 60 3.1.4 Sample STL, Stateful –Tour package ................................................................................ 70
Sabre Inc. Confidential/All Rights Reserved Error! No text of specified style in document. vi
D e f i n e d E r r o r s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 8
4.1 Error List ..................................................................................................................................... 78 4.2 Sample Error RS ........................................................................................................................ 80
F r e q u e n t l y A s k e d Q u e s t i o n s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1
5.1 Who should I contact for query help ........................................................................................... 81 5.2 First Level Support ..................................................................................................................... 81
Sabre Inc. Confidential/All Rights Reserved Process Overview 7
1 . 1 . I n t r o d u c t i o n
This guide is for architects and developers to learn how to compose XML formatted requests for
CreateReservationRQ Web Service. This release covers the XML request and responses which allow
client applications to make one call to the host to create PNR data including Itinerary (Rail), and
Passenger information, etc (details below). CreateReservationRS message can be returned in STL,
respective details can be found in the WSDL file.
1 . 2 . D e s c r i p t i o n
This Web Service offers capabilities allowing Airline or Agencies to create PNR data. The request can be
further detailed by the ReturnOption section which specifies content of the return message.
sd CreateReservationRQ
WS Consumer CreateReservationRQPassenger Service System
(Sabre)
Request
Response with 1 PNR (STL) or error message
Validate Request
Stateless/Stateful RQ
Stateless/Stateful RS
Request Type, Return Options
Process Overview 1
Sabre Inc. Confidential/All Rights Reserved Process Overview 8
The PNR will be created using one of the available request types: Stateless and Stateful; and by one of the
two following processes.
Stateless: Full data provided at creation; ET at end with Locator
All necessary data is provided in RQ;
After being created the PNR will be committed;
It is required to provide “ReceivedFrom” element in the RQ;
“Locator” element will be returned in the RS.
Stateful: Data provided at creation, NO ET at end, no Locator
All necessary data is not provided in RQ;
After being created the PNR will not be committed;
It is required to provide “ReceivedFrom” element in the RQ;
Remaining details for completing the PNR are entered via Host Sabre via commands – or using
UpdateReservationRQ;
After being updated the PNR will be committed.
CreateReservationRQ Web Service allows client applications to create the PNR in STL data format.
“ReturnOptions” element can be used to specify which data elements will be present in response
payload,
IncludeUpdateDetails=”true”
RetrievePNR=”true”
“ReturnOptions” element can be used to specify how the data elements will be formatted:
XML “ResponseFormat” - STL;
“SubjectAreas”;
“ViewName”;
When using pnrbuilder files on versions higher than v1.7.8 you will need to be specify the version
number in the namespace
<CreateReservationRQ Version="1.11.0" xmlns="http://webservices.sabre.com/pnrbuilder/v1_11">
Sabre Inc. Confidential/All Rights Reserved Process Overview 9
1 . 3 . V i e w s a n d S u b j e c t A r e a s
PNR data which will be present in a response payload depends on a View Name used in request. Number
of data elements returned in each View can be further narrowed by Subject Areas. If data elements
corresponding to particular Subject Area are not present in the PNR then those will not be returned in
response payload. The most common View Types and Subject Areas are listed below. Custom made
Views and Subject Areas may be developed if required.
View Description
Simple Response payload will contain only, basic, header data.
Multiple Subject Areas may be specified in the request payload.
Full Response payload will contain PNR data specified by all Subject Areas.
Default Response payload will contains PNR data
Subject Area Description
HEADER PNR header
NAME Passenger Name
RECEIVED Received from
PHONE Phone number(s)
FQTV Frequent Traveler Number
ADDRESS Address data
DKNUMBER Customer number - agencies use the DK number primarily as an account reference
identifier for billing purposes
CUST_INSIGHT_PROFILE Customer Profile Number
CORPORATE_ID Agency ID for corporate client
PASSENGERDETAILS Profile data, passenger type, email address
PRERESERVEDSEAT Pre reserved seat data
AFAX All facts stored in the PNR
GFAX General facts stored in PNR
REMARKS All remarks in PNR
BSGPROCESSING Block Space Group information
FARETYPE Fare information
ACCOUNTING_LINE Agency accounting line(s)
TICKETING Ticketing information
ITINERARY Full itinerary including Air, Car, Hotel etc.
ANCILLARY Ancillary (Air Extra) Items
Sabre Inc. Confidential/All Rights Reserved Process Overview 10
1 . 4 . N e w F e a t u r e s i n t r o d u c e d i n C r e a t e R e s e r v a t i o n
s e r v i c e
Feature Description
Rail Segment
Providing agencies the ability to sell Rail content via Sabre Rail
Webservices.
For more details on the feature reference Sabre SAN Notification
8131.
Tour Segments Providing agencies the ability to sell Tour segments.
Sabre Inc. Confidential/All Rights Reserved Process Overview 11
1 . 5 . G l o s s a r y
Term Explanation
AAA Agent Assembly Area – refers to the buffer in the Sabre system where
content is retained while a Sabre Host session is active.
FOID Form of Identification is used to advise carrier what identification the
passenger will present upon check-in for e-ticket travel
Locator PNR locator
OAC Office Accounting Code is used to identify customer office locations
OSI Other Supplementary Information can be used when action or reply
from carrier is not required
PCC Pseudo City Code uniquely identifies travel agency in the same way
that a city code identifies a city
PNR Passenger Name Record
POS Point of Sale
PSS Passenger Service System also known as Sabre Host
SAN Sabre Advance Notification
SSR Special Service Request is used when action or response from carrier is
required
STL SABRE XML format
Segment Itinerary field of a Passenger Name Record holding actual booking (Air,
Car, Hotel etc.)
Sabre Inc. Confidential/All Rights Reserved Request parameters 12
Below there is a list of selected request elements (RQ) which can be combined to create a request
message. In response (RS) user will be provided with XML containing details for requested PNR.
Response message can be returned in STL format, for more information please refers to corresponding
XSD files.
Following descriptions contain basic information about particular elements, though primary source of
knowledge should be corresponding XSD files.
2 . 1 ( R Q ) R e q u e s t T y p e
Element: RequestType
RequestType Attributes: commitTransaction, initialIgnore
RequestType is used to define how PNR data will be created. It can be set to: Stateless, Stateful.
commitTransaction allows control if End Transaction should be called at the end of a Stateful call. This
option is ignored in Stateless call. By default it is set to false.
initialIgnore allows control if Ignore (IG) should be called at the beginning of a Stateful call. This
option is ignored in Stateless call. By default it is set to false.
Stateless: Full data provided at creation; ET at end with Locator
All necessary data is provided in RQ;
After being created the PNR will be committed;
It is required to provide “ReceivedFrom” element in the RQ;
“Locator” element will be returned in the RS.
Stateful: Data provided at creation, NO ET at end, no Locator
All necessary data is not provided in RQ;
After being created the PNR will not be committed;
It is required to provide “ReceivedFrom” element in the RQ;
Remaining details for completing the PNR are entered via Host Sabre via commands – or using
UpdateReservationRQ;
After being updated the PNR will be committed.
Request parameters 2
Sabre Inc. Confidential/All Rights Reserved Request parameters 13
2 . 2 ( R Q ) R e t u r n O p t i o n s
Element: ReturnOptions
Sub Elements: SubjectAreas; ViewName ;ResponseFormat
ReturnOptions Attributes: UnmaskCreditCard, RetrievePNR, IncludeUpdateDetails, ReturnLocator
Return Options are used to define format and data range of response payload. See section 1.3 Views and Subject
Areas for more details.
The PNR data present in the response payload depends on the specified View Name used in the request.
Number of data elements returned in each View can be further narrowed using the optional values of
RetrievePNR or IncludeUpdateDetails.
ReturnOptions contains the attribute UnmaskCreditCard and by default the value of the attribute is false. When a
request is made with this attribute as true the user must have the EPR keyword CCVIEW; in the response the
credit card information will be presented in unmasked format, else the credit card information will always be in
masked format.
SubjectArea specifies particular information to be included in response message if they are stored in the PNR. It
can be set to e.g.: "ITINERARY","ADDRESS", "HEADER", "NAME" etc.
ReturnOptions contains the attribute ReturnLocator which determines if the response should contain locator
information if available during update operation. This setting is independent of RetrievePNR setting.
ResponseFormat enables the user to define how the response payload will be formatted and value should be STL.
2 . 3 ( R Q ) P O S
Element: POS
Sub Elements: Source
Source holds details regarding the requestor. It may be repeated to also accommodate the delivery system.
2 . 4 ( R Q ) S o u r c e
Element: Source
Sub Elements: RequestorID, BookingChannel, TTYRecordLocator, OAC
Source Attributes:
BookingSource, AgentSine, PseudoCityCode, ISOCountry, ISOCurrency,
AgentDutyCode, AirlineVendorID, AirportCode, FirstDepartPoint, SourceSystem,
TerminalID
Source holds details regarding the requestor. It may be repeated to also accommodate the delivery system.
Sabre Inc. Confidential/All Rights Reserved Request parameters 14
BookingSource identifies the booking source within the requesting entity.
AgentSine identifies the party within the requesting entity.
PseudoCityCode an identification code assigned to an office/ agency by a reservation system.
ISOCountry the country code of the requesting party.
AgentDutyCode an authority code assigned to a requestor.
AirlineVendorID the IATA assigned airline code.
AirportCode the IATA assigned airport code.
FirstDepartPoint the point of first departure in a trip.
SourceSystem e.g., CSS or CSI
TerminalID the electronic address of the device from which information is entered.
RequestorID is an identifier of the entity making the request e.g., ATA/IATA/ID number, Electronic Reservation
Service Provider (ERSP), Association of British Travel Agents (ABTA).
BookingChannel specifies the booking channel type and whether it is the primary means of connectivity of the
source.
OAC the Office Account Code defines the agency PCC extension.
2 . 5 ( R Q ) R e q u e s t o r I D
Element: RequestorID
Sub Elements: CompanyName, ArrangerDetails
RequestorID Attributes: URL, Type, Instance, ID, ID_Context, MessagePassword
RequestorID is used to enter an identifier of the entity making the request.
URL identifies the location associated with the record identified by the UniqueID.
Type a reference to the type of object defined by the UniqueID element. Refer to OTA code List Unique ID Type
(UIT).
Instance the identification of a record as it exists at a point in time. An instance is used in update messages where
the sender must assure the server that the update sent refers to the most recent modification level of the object
being updated.
ID a unique identifying value assigned by the creating system. The ID attribute may be used to reference a
primary-key value within a database or in a particular implementation.
ID_Context used to identify the source of the identifier e.g., IATA, ABTA.
MessagePassword this password provides an additional level of security that the recipient can use to validate the
sending party’s authority to use the message.
CompanyName identifies the company that is associated with the UniqueID.
Sabre Inc. Confidential/All Rights Reserved Request parameters 15
2 . 6 ( R Q ) C o m p a n y N a m e
Element: CompanyName
ComapnyName
Attributes: CompanyShortName, TravelSector, Code, CodeContext, Division, Department
CompanyName is used to enter the name of the company making the request.
CompanyShortName used to provide the company common name.
TravelSector refer to OTA Code List Travel Sector (TVS).
Code Identifies a company by the company code.
CodeContext identifies the context of the identifying code, such as DUNS, IATA or internal code.
Division the division name or ID with which the contact is associated.
Department the department name or ID with which the contact is associated.
2 . 7 ( R Q ) A r r a n g e r D e t a i l s
Element: ArrangerDetails
Sub Elements: PersonName, Telephone, Email
ArrangerDetails are used to identify the details of the requestor.
2 . 8 ( R Q ) P e r s o n N a m e
Element: PersonName
Sub Elements: Prefix, Given, Middle, Surname, Suffix, Type, PreferredFirstName,
PreferredSurname
PersonName is used to enter contact information to the PNR.
Prefix a salutation of honorific e.g., Mr., Mrs., Ms., Miss., Dr.
Given the given name, first name or names.
Middle the middle name of the person name.
Required sub element. Surname the family name also known as last name.
Suffix holds various name suffixes and letters e.g., Jr., Sr., III., Ret., Esq.
PreferredFirstname any preferred name for first name used instead of the GivenName.
PreferredSurname any preferred names for last name used instead of Surname.
Sabre Inc. Confidential/All Rights Reserved Request parameters 16
2 . 9 ( R Q ) T e l e p h o n e
Element: Telephone
Sub Elements: PhoneUseType, PhoneCountryCode, PhoneCountryName, PhoneNumber
Telephone is used to identify the telephone details of the contact in the PNR.
PhoneNumber is required.
2 . 1 0 ( R Q ) B o o k i n g C h a n n e l
Element: BookingChannel
Sub Elements: CompanyName
BookingChannel
Attributes: Type, Primary
BookingChannel is used to enter the details of how the PNR is created.
Type the type of booking channel e.g., Global Distribution System (GDS), Alternative Distribution System (ADS),
Sales and Catering System (SCS), Property Management System (PMS), Central Reservation System (CRS), Tour
Operator System (TOS), Internet and ALL. Refer to OTA Code List Booking Channel Type (BCT).
Primary indicates whether the enumerated booking channel is the primary means of connectivity used by the
source.
2 . 1 1 ( R Q ) T T Y R e c o r d L o c a t o r
Element: TTYRecordLocator
Sub Elements: CRSLocator, CRSCode, RecordLocator, AgencyId, IataNumber, AgencyLocation,
UserType, CountryCode, Currency, DutyCode, ERSPUserId, FirstPointOfDeparture
TTYRecordLocator identifies how the record is created.
AgencyId is the booking source arranger.
IataNumber is the booking source location IATA number.
AgencyLocation is the booking source agent location.
UserType includes the values of A-Airline, E-ERSP, N-no user ID assigned by IATA, T-user ID assigned by
IATYA other than ERSP.
ERSPUserId is the Electronic Reservation ServiceProvider number.
FirstPointOfDeparture the first point of departure for the booking.
Sabre Inc. Confidential/All Rights Reserved Request parameters 17
2 . 1 2 ( R Q ) O A C
Element: OAC
Sub Elements: PartitionId, AccountingCityCode, AccountingCode, AccountingOfficeStationCode
PartitionId is the default partition code from the OAC data.
AccountingCityCode the personal account city code associated with user AAA city during the original PNR create
session.
AccountingCode the personal account code associated with user AAA city during the original PNR create session.
AccountingOfficeStationCode the station code from the OAC line used in the PNR create session.
2 . 1 3 ( R Q ) N e w R e s e r v a t i o n
Elements:
Itinerary, PersonName, PhoneNumber, Profile, DKNumber, TicketingInfo, Remark,
OtherServiceInformation, ReceivedFrom, CustomEntry, EmailAddress,
AccountingLine
DkNumber Attribute: op
New Reservation is the creation of a new reservation including all of segments present in the PNR.
op attribute can be used to specify operation type as follows: C=Create, U=Update, D=Delete.
2 . 1 4 ( R Q ) I t i n e r a r y
Elements: Product; ProductBase; ProductDetails; AdditionalContent
Itinerary is the listing of a reservation including all of segments present in the PNR.
2 . 1 5 ( R Q ) P r o d u c t
Elements: Product
Sub Elements: ProductBase; ProductDetails; AdditionalContent
Product Attributes: sequence, id, IsPast
AdditionalContent
Attributes: persist, name
Product is the listing of the details about the segment.
id attribute can be used to specify explicit reference to PNR Lrec.
Sabre Inc. Confidential/All Rights Reserved Request parameters 18
IsPast returns information if the current segment is past or not.
IsPast attribute is populated based on Product/ProductBase/ EndDateTime, and Product/ProductBase/Endpoint.
AdditionalContent can be any text entered.
2 . 1 6 ( R Q ) P r o d u c t B a s e
Elements: ProductBase
Sub Elements: ProductType; VendorCode; StatusCode; StartPoint; StartDateTime; EndPoint;
EndDateTime; Text; SegmentReference
ProductBase includes the basic definitions of the segment.
Required elements include ProductType, VendorCode, StartPoint, StartDateTime and SegmentReference.
2 . 1 7 ( R Q ) P r o d u c t D e t a i l s
Elements: ProductDetails
Sub Elements: ProductName; ExternalSystemReference; TransactionInfo; CO2Value; one of Hotel,
GroundTransportation or Rail
ProductDetails
Attributes:
productCategory; productType; vendorCode; statusCode; previousStatusCode;
startPoint; startDateTime; endPoint; endDateTime; normalizedIndicator
ProductName Attribute: type
ExternalSystemReference
Attributes: ID, Source
CO2Value Attribute: unit
ProductDetails allows users to provide information about the segment to the service.
Includes one of Hotel, GroundTransportation or Rail.
productCategory includes values like TruTrip, passive, high level source/type.
normalizedIndicator when equals to true means this data has been normalized with Normalized Services.
ExternalSystemReference is a HOLD reference ID given by external system/application which can be used to
reference to product item that is in the external system.
ExternalSystemReference@ID is the HOLD reference ID
ExternalSystemReference@Source is the HOLD information of the source of this reference ID.
CO2Value@unit holds information about the CO2 emission unit.
Sabre Inc. Confidential/All Rights Reserved Request parameters 19
2 . 1 8 ( R Q ) H o t e l
Elements: Hotel
Sub Elements: Reservation; AdditionalInformation; SegmentText; RateDescription; HotelPolicy;
SupplementalInformation
Hotel Attributes: index; id; sequence; isPast
Hotel is used to add Hotel segment details to the itinerary.
sequence attribute identifies the sequence number of the Itinerary.
isPast attribute returns information if the current element is past or not.
2 . 1 9 ( R Q ) R e s e r v a t i o n
Elements: Reservation
Sub Elements:
LineNumber; LineType; LineStatus; POSRequestorID: SpecialPrefs; RoomType;
RoomRates; RateAccessCodeBooked; GuestCounts; TimeSpanStart;
TimeSpanDuration; TimeSpanEnd; Guarantee; ChainCode; HotelCode;
HotelCityCode; HotelName; HotelTotalPricing; HotelUniqueID;
HotelCode Attribute: Source
HotelUniqueId Attributes: Source, ID
Reservation includes the hotel reservation information.
TimeSpanStart is the starting value of the time span.
TimeSpanDuration the lexical representation for timeDuration is the (ISO 8601) extended format
PnYnMnDTnHnMnS, where nY represents the number of years, nM the number of months, nD the number of
days, T is the date/time separator, nH the number of hours, nM the number of minutes and nS the number of
seconds. The number of seconds can include decimal digits to arbitrary precision. So 7 months, 2 days, 2 hours
and 30 minutes would be expressed as P0Y7M2DT2H20M0S.
TimeSpanEnd the ending value of the time span.
ChainCode the code that identifies a hotel chain or management group. The hotel chain code is decided between
vendors. This attribute is optional if the hotel is an independent property that can be identified by the HotelCode
attribute.
HotelCode is the code that uniquely identifies a single hotel property. The hotel code is decided between
vendors. The Source Attribute holds the source of this Hotel Code which could be an external application or
system.
HotelCityCode the IATA city code e.g., DCA, ORD.
HotelName a text field used to communicate the proper name of the hotel.
HotelUniqueID attributes of Source – the application/system that is the source of this Hotel ID and ID the Hotel
ID.
Sabre Inc. Confidential/All Rights Reserved Request parameters 20
2 . 2 0 ( R Q ) S p e c i a l P r e f s
Elements: SpecialPrefs
Sub Elements: Text
SpecialPrefs is an unbound text element to add comments about special hotel preferences.
2 . 2 1 ( R Q ) R o o m T y p e
Elements: RoomType
Sub Elements: RoomTypeCode; NumberOfUnits; ShortText
RoomType is a summary version of the Room Type initially created for the Travel Itinerary Message set.
RoomTypeCode a specific system room type code e.g., A1K, A1Q, A1F, etc.
2 . 2 2 ( R Q ) R o o m R a t e s
Elements: RoomRates
Sub Elements: AmountBeforeTax; CurrencyCode; Override
RoomRates show the reservation rate(s).
2 . 2 3 ( R Q ) R a t e A c c e s s C o d e B o o k e d
Elements: RateAccessCodeBooked
Sub Elements: ClientIdentificationCode; RateAccessCode; CategoryTypeCode
RateAccessCodeBooked describes the Hotel ClientIdentificationCode, RateAccessCode and the
CategoryTypeCode for the reservation booked.
2 . 2 4 ( R Q ) G u e s t C o u n t s
Elements: GuestCounts
Sub Elements: GuestCount; ExtraGuestCount; RollAwayCount; CribCount; ReserveUnderName;
Name
GuestCounts is used to add details about the number of guests associated with this reservation and if any extra
beds are requested, e.g., crib or rollaway bed.
Sabre Inc. Confidential/All Rights Reserved Request parameters 21
2 . 2 5 ( R Q ) G u a r a n t e e
Elements: Guarantee
Sub Elements: PaymentCardNumber; Text
Guarantee is used to add a credit card and text to the reservation.
2 . 2 6 ( R Q ) H o t e l T o t a l P r i c i n g
Elements: HotelTotalPricing
Sub Elements: TotalTax; TotalSurcharge; ApproximateTotal; RateChange; Disclaimer
HotelTotalPricing
Attribute: CurrencyCode
ApproximateTotal
Attribute: AmountAndCurrency
RateChange Attributes: Id, Amount, Effective, Surcharge, Tax
Disclaimer Attribute: Id
HotelTotalPricing is used to enter the Pricing information on the Hotel reservation.
CurrencyCode is the code specifying a monetary unit. Use ISO 4217 three digit alpha code.
2 . 2 7 ( R Q ) T o t a l T a x
Elements: TotalTax
Sub Elements: Tax
TotalTax Attribute: Amount
Tax Attribute: Id
TotalTax is the Amount and Id of the amount to be charged for the Hotel reservation.
2 . 2 8 ( R Q ) T o t a l S u r c h a r g e
Elements: TotalSurcharge
Sub Elements: Surcharge
Sabre Inc. Confidential/All Rights Reserved Request parameters 22
TotalSurcharge Attribute: Amount
Surcharge Attribute: Id
TotalSurcharge is the Amount and Id of the amount of the surcharge for the Hotel reservation.
2 . 2 9 ( R Q ) H o t e l U n i q u e I D
Elements: HotelUniqueId
HotelUniqueId Attribute: Source, ID
HotelUniqueID is used to identify the Hotel by Source and Id in the reservation.
Source attribute is the application/system that is the source of the Hotel ID.
ID attribute is the Hotel ID.
2 . 3 0 ( R Q ) A d d i t i o n a l I n f o r m a t i o n
Elements: AdditionalInformation
Sub Elements:
ConfirmationNumber; Address; ContactNumbers; CancelPenaltyPolicyCode;
CustLoyaltyMembershipID; IDNumber; CorporateIDNumber; Text; Commission;
WrittenConfirmation
ConfirmationNumber
Attributes: Source, DirectConnect
AdditionalInformation is used to add other details to the reservation.
Source attribute is the source of this confirmation number.
DirectConnect is set if hotel was sold via Direct Connect Channel.
2 . 3 1 ( R Q ) A d d r e s s ( H o t e l )
Elements: Address
Sub Elements: AddressLine; CountryCode; City; State; ZipCode
Address is used to add address details in the Hotel reservation.
2 . 3 2 ( R Q ) C o n t a c t N u m b e r s
Elements: ContactNumbers
Sabre Inc. Confidential/All Rights Reserved Request parameters 23
Sub Elements: PhoneNumber; FaxNumber
ContactNumbers is used to add contact information to the Hotel reservation.
2 . 3 3 ( R Q ) C o m m i s s i o n
Elements: Commission
Sub Elements: Indicator; PerNight; Text
Commission is used to add details of commission that should be added to the Hotel reservation.
2 . 3 4 ( R Q ) R a t e D e s c r i p t i o n
Elements: RateDescription
Sub Elements: TextLine
RateDescription is used to add text relating to the Hotel reservation.
2 . 3 5 ( R Q ) H o t e l P o l i c y
Elements: HotelPolicy
Sub Elements: DepositPolicy; GuaranteePolicy; LateArrivalPolicy; CancellationPolicy;
AdditionalPolicy; CheckInCheckOutPolicy
CheckInCheckOutPolicy
Attributes: CheckIn, CheckOut
HotelPolicy is used to add specific policy information regarding the Hotel reservation.
AdditionalPolicy includes a sub element of TextLine to allow unlimited text to be added.
CheckIn is the check-in time policy used to inform guests that they should check in after this check-in time.
CheckOut is the check-out time policy used to inform guests that they should check out after this check-out time.
2 . 3 6 ( R Q ) G r o u n d T r a n s p o r t a t i o n
Elements: GroundTransportation
Sub Elements:
StatusCode; Vendor; Service; ServiceProvider; StartDetails; StopDetails;
EndDetails; ExternalReservation; Restrictions; POS; AgentLoyalty; Passenger;
RateQualifier; Charges
GroundTransportation is used to add ground transportation segment details to the itinerary.
Sabre Inc. Confidential/All Rights Reserved Request parameters 24
2 . 3 7 ( R Q ) V e n d o r
Elements: Vendor
Sub Elements: Name; Code; Telephone; Address
Code Attribute: codeContext
Vendor and is used to add the ground transportation vendor contact details to the itinerary.
2 . 3 8 ( R Q ) A d d r e s s ( G r o u n d T r a n s p o r t a t i o n o r R a i l )
Elements: Address
Sub Elements:
LocationType; AddressLine; CityName; CityCodes; LocalCityName; StateProvince;
StateProvinceCodes; PostCode; Country: CountryCodes; Latitude; Longitude;
Altitude
StateProvince Attribute: code
Country Attribute: code
Address is used to add appropriate vendor or service provider contact address details of the segment to the
itinerary.
2 . 3 9 ( R Q ) C i t y C o d e s
Elements: CityCodes
Sub Elements: Code
Code Attribute: codeContext
CityCodes is used to add the appropriate city code to the ground transportation vendor address in the itinerary.
2 . 4 0 ( R Q ) S t a t e P r o v i n c e C o d e s
Elements: StateProvinceCodes
Sub Elements: Code
Code Attribute: codeContext
StateProvinceCodes is used to add the appropriate state or province code to the ground transportation vendor
Sabre Inc. Confidential/All Rights Reserved Request parameters 25
address in the itinerary.
2 . 4 1 ( R Q ) C o u n t r y C o d e s
Elements: CountryCodes
Sub Elements: Code
Code Attribute: codeContext
CountryCodes is used to add the appropriate country code to the ground transportation vendor address in the
itinerary.
2 . 4 2 ( R Q ) S e r v i c e
Elements: Service
Sub Elements: ServiceLevel; Equipment; Meet AndGreetInd; MaximumBaggage;
MaximumPassengers
Service is used to add the appropriate details to the ground transportation segment in the itinerary.
2 . 4 3 ( R Q ) S e r v i c e L e v e l
Elements: ServiceLevel
Sub Elements: Code; Description; Level
ServiceLevel is used to add the appropriate details to the ground transportation segment in the itinerary.
2 . 4 4 ( R Q ) E q u i p m e n t
Elements: Equipment
Sub Elements: Code; Type; Description
Equipment is used to add the appropriate equipment details to the ground transportation segment in the itinerary.
2 . 4 5 ( R Q ) S e r v i c e P r o v i d e r
Elements: ServiceProvider
Sub Elements: Name; Code; Telephone; Address
Sabre Inc. Confidential/All Rights Reserved Request parameters 26
ServiceProvider is used to add the appropriate contact details to the ground transportation segment in the
itinerary.
2 . 4 6 ( R Q ) C o d e
Elements: Code
Sub Elements: codeContext
Code is used to add the appropriate details to the service provider of the appropriate segment in the itinerary.
2 . 4 7 ( R Q ) S t a r t D e t a i l s
Elements: StartDetails
Sub Elements: Address; DateTime; AirportInfo; RailwayStationInfo; Comments
StartDetails is used to add the appropriate details of the segment in the itinerary.
2 . 4 8 ( R Q ) A i r p o r t I n f o
Elements: AirportInfo
Sub Elements: Airline; AirportName; LocationCode; Terminal; Gate
Airline Attributes: code, flightNumber, flightDateTime, flightType, privateAviation
AirportInfo is used to add the appropriate airport details of the segment in the itinerary.
2 . 4 9 ( R Q ) R a i l w a y S t a t i o n I n f o
Elements: RailwayStationInfo
Sub Elements: StationName; LocalStationName; LocationCodes; Amenities
RailwayStationInfo
Attribute: borderPoint
StationName Attribute: Lang
LocalStationName
Attribute: Lang
RailwayStationInfo is used to add the appropriate station details of the segment in the itinerary.
Sabre Inc. Confidential/All Rights Reserved Request parameters 27
2 . 5 0 ( R Q ) L o c a t i o n C o d e s
Elements: LocationCodes
Sub Elements: Code
Code Attribute: codeContext
LocationCodes is used to add the appropriate details of the ground transportation segment in the itinerary.
2 . 5 1 ( R Q ) A m e n i t i e s
Elements: Amenities
Sub Elements: Amenity
Amenity is used to add the appropriate details of the ground transportation segment in the itinerary.
2 . 5 2 ( R Q ) S t o p D e t a i l s
Elements: StopDetails
Sub Elements: Address; DateTime; AirportInfo; RailwayStationInfo; Comments
StopDetails is used to add the appropriate details of the segment in the itinerary.
2 . 5 3 ( R Q ) E n d D e t a i l s
Elements: EndDetails
Sub Elements: Address; DateTime; AirportInfo; RailwayStationInfo; Comments
EndDetails is used to add the appropriate details of the segment in the itinerary.
2 . 5 4 ( R Q ) E x t e r n a l R e s e r v a t i o n
Elements: ExternalReservation
Sub Elements: SourceSystem; ConfirmationNumber; CancellationNumber; ReferenceNumber;
ReservationStatus
ExternalReservation is used to add the appropriate details of the ground transportation segment in the itinerary.
Sabre Inc. Confidential/All Rights Reserved Request parameters 28
2 . 5 5 ( R Q ) R e s t r i c t i o n s
Elements: Restrictions
Sub Elements: CancelPolicy; TextLine
Restrictions allow the user to add the appropriate cancellation details of the ground transportation segment in the
itinerary.
2 . 5 6 ( R Q ) A g e n t L o y a l t y
Elements: AgentLoyalty
Sub Elements: ProgramName; MembershipID; LoyaltyLevel; EffectiveDate; ExpireDate; Remark
LoyaltyLevel Attribute: code
AgentLoyalty is used to add the appropriate loyalty program details of the ground transportation segment in the
itinerary.
2 . 5 7 ( R Q ) P a s s e n g e r
Elements: Passenger
Sub Elements: Type; PersonName; Telephone; Email
Passenger Attributes: passengerID, primary
Type Attributes: code, codeContext
Passenger is used to add the appropriate passenger details of the segment in the itinerary.
2 . 5 8 ( R Q ) R a t e Q u a l i f i e r
Elements: RateQualifier
Sub Elements: AccountID; AccountName; PromotionCode; SpecialInput
SpecialInput Attribute: name
RateQualifier is used to add the appropriate qualifier details of the ground transportation segment in the itinerary.
Sabre Inc. Confidential/All Rights Reserved Request parameters 29
2 . 5 9 ( R Q ) C h a r g e s
Elements: Charges
Sub Elements: GeneralNotes; Charge; GrandTotal; GeneralBillingType
GrandTotal Attribute: currencyCode
Charges allow the user to add the appropriate cost details of the segment in the itinerary.
2 . 6 0 ( R Q ) C h a r g e
Elements: Charge
Sub Elements: Description; Notes; Name; Calculation; BillingType
Charge Attribute: currencyCode
Charge is used to add the appropriate cost details of the segment in the itinerary.
2 . 6 1 ( R Q ) C a l c u l a t i o n
Elements: Calculation
Sub Elements: UnitName; UnitCharge; Quantity; Total
UnitCharge Attributes: min, max
Quantity Attributes: min, max
Total Attributes: min, max
Calculation is used to add the appropriate cost details of the segment in the itinerary.
2 . 6 2 ( R Q ) R a i l
Elements: Rail
Sub Elements:
StatusCode; Open; CrossBorder; Duration; MarketingCarrier; OperatingCarrier;
Passengers; SupplementaryServices; TrainInfo; Accommodation; StartDetails;
StopDetails; EndDetails; RailFares; Documents; Details
Rail is used to add the appropriate details of the Rail segment in the itinerary.
Sabre Inc. Confidential/All Rights Reserved Request parameters 30
2 . 6 3 ( R Q ) M a r k e t i n g C a r r i e r
Elements: MarketingCarrier
Sub Elements: Name; Code; Telephone; Address
MarketingCarrier is used to add the appropriate details about the marketing carrier of the Rail segment in the
itinerary.
2 . 6 4 ( R Q ) O p e r a t i n g C a r r i e r
Elements: OperatingCarrier
Sub Elements: Name; Code; Telephone; Address
OperatingCarrier is used to add the appropriate details about the operating carrier of the Rail segment in the
itinerary.
2 . 6 5 ( R Q ) P a s s e n g e r s
Elements: Passengers
Sub Elements: Passenger
Passengers Attribute: quantity
Passenger is used to add the appropriate passenger details of the segment in the itinerary.
2 . 6 6 ( R Q ) S u p p l e m e n t a r y S e r v i c e s
Elements: SupplementaryServices
Sub Elements: SupplementaryService
SupplementaryServices is used to add the appropriate additional service details of the segment in the itinerary.
Sabre Inc. Confidential/All Rights Reserved Request parameters 31
2 . 6 7 ( R Q ) S u p p l e m e n t a r y S e r v i c e
Elements: SupplementaryService
Sub Elements: Description; Charges; PassengerReferences
SupplementaryService
Attributes: type, code, codeContext
Description Attribute: lang
SupplementaryServics is used to add the appropriate additional service details of the segment in the itinerary.
2 . 6 8 ( R Q ) P a s s e n g e r R e f e r e n c e s
Elements: Passenger References
Sub Elements: Passenger Ref
Passenger Ref
Attribute: id
PassengerReferences is used to add a reference for a specific passenger to the segment in the itinerary.
2 . 6 9 ( R Q ) T r a i n I n f o
Elements: TrainInfo
Sub Elements: Number; Code; ShortName; LongName
TrainInfo is used to add a reference for Rail service of the segment in the itinerary.
2 . 7 0 ( R Q ) A c c o m m o d a t i o n
Elements: Accommodation
Sub Elements: PassengerRef; Placement; Meal
Accommodation is used to add details on accommodation location of Rail service passengers of the segment in
the itinerary.
2 . 7 1 ( R Q ) P l a c e m e n t
Elements: Placement
Sabre Inc. Confidential/All Rights Reserved Request parameters 32
Sub Elements: Coach; Detail
Placement Attributes: code, type
Placement is used to add details on accommodation location of Rail service passengers of the segment in the
itinerary.
2 . 7 2 ( R Q ) C o a c h
Elements: Coach
Sub Elements: CoachNumber; PlacementNumber; CompartmentNumber
PlacementNumber
Attribute: compartmentRefId
Coach is used to add details on accommodation location of Rail service passengers of the segment in the
itinerary.
2 . 7 3 ( R Q ) R a i l F a r e s
Elements: RailFares
Sub Elements: Fare
RailFares is used to add details on the cost of the Rail service segment in the itinerary.
2 . 7 4 ( R Q ) F a r e
Elements: Fare
Sub Elements: PassengerReferences; SegmentReferences; ClassOfService; ClassCode;
FareDescription; FarePrice
ClassOfService
Attributes: code, type
ClassCode Attributes: code, type
FarePrice Attribute: currencyCode
Fare is used to add details on the Rail service segment in the itinerary.
Sabre Inc. Confidential/All Rights Reserved Request parameters 33
2 . 7 5 ( R Q ) S e g m e n t R e f e r e n c e s
Elements: SegmentReferences
Sub Elements: SegmentRef
SegmentRef Attribute: id
SegmentReferences is used to add details on the Rail service segment in the itinerary.
2 . 7 6 ( R Q ) F a r e D e s c r i p t i o n
Elements: FareDescription
Sub Elements: Name; Code; Detail; Condition; Fees
Detail Attribute: Type, codeContext
Condition Attribute: lang
FareDescription is used to add details on the cost of the Rail service segment in the itinerary.
2 . 7 7 ( R Q ) F e e s
Elements: Fees
Sub Elements: Fee; Amount; Description
Fee Attributes: name, type, currencyCode
Fees is used to add details on the cost of the Rail service segment in the itinerary.
2 . 7 8 ( R Q ) D o c u m e n t
Elements: Document
Sub Elements:
DocumentID; AgencyAccountNumber; CreationChannel; PassengerReferences;
SegmentReferences; IssueTimeLimit; IssueDateTime; DocumentStatus; Charges;
FormOfPayment; File; IssueType; DocumentRules
Document Attributes: type, code, codeContext
Document is used to add details on the Rail service segment in the itinerary.
Sabre Inc. Confidential/All Rights Reserved Request parameters 34
2 . 7 9 ( R Q ) F o r m O f P a y m e n t
Elements: FormOfPayment
Sub Elements: CreditCard; Cash; Check; Voucher; Other
FormOfPayment
Attributes: transactionID
FormOfPayment is used to add payment details on the Rail service segment in the itinerary.
2 . 8 0 ( R Q ) C r e d i t C a r d
Elements: CreditCard
Sub Elements: Number; Issuer; ExpirationMonth; ExpirationYear; CardHolder
CreditCard is used to add credit card payment details on the Rail service segment in the itinerary.
2 . 8 1 ( R Q ) C a r d H o l d e r
Elements: CardHolder
Sub Elements: PersonName; Address; Telephone; Email
CardHolder is used to add credit card contact details on the Rail service segment in the itinerary.
2 . 8 2 ( R Q ) F i l e
Elements: File
Sub Elements: Representation; URL
File Attributes: type, coding
File is used to add details on the Rail service segment in the itinerary.
2 . 8 3 ( R Q ) D o c u m e n t R u l e s
Elements: DocumentRules
Sub Elements: Exchangeable; Refundable; Rule
Sabre Inc. Confidential/All Rights Reserved Request parameters 35
Rule Attributes: type
DocumentRules is used to add details on the Rail service segment in the itinerary.
2 . 8 4 ( R Q ) T r a n s a c t i o n I n f o
Elements: TransactionInfo
Sub Elements: RequestorInfo
TransactionInfo Attribute: LastUpdateTimeStamp
RequestorInfo Attribute: AgentSine; PseudoCityCode; AgentDutyCode; AirportCode; TerminalID;
ApplicationID
LastUpdateTimeStamp indicates the creation date and time of the message in UTC using the format YYYY-MM-
DDThh:mmm:ssZ with time values using the 24 hour clock e.g., 20 November 2003, 1:59:38 pm UTC becomes
2003-11-20T13:59:38.
AgentSine identifies the party within the requesting entity.
PseudoCityCode an identification code assigned to an office/agency by a reservation system.
AgentDutyCode an authority code assigned to a requestor.
AirportCode the IATA assigned airport code.
TerminalID this is the electronic address of the device from which the payload is submitted.
ApplicationID the identifier of the calling application that is used by this requestor to submit this payload.
Required attribute.
2 . 8 5 ( R Q ) P e r s o n N a m e ( N e w R e s e r v a t i o n )
Elements: PersonName
Sub Elements: Given; Surname; Prefix
PersonName Attributes: type, referenceId
PersonName is used to add the contact details for the person in the PNR.
2 . 8 6 ( R Q ) P h o n e N u m b e r
Elements: PhoneNumber
Sub Elements: PhoneText
PhoneNumber Attributes: id, op
PhoneNumber is used to add the contact number for the person in the PNR.
Sabre Inc. Confidential/All Rights Reserved Request parameters 36
id attribute can be used to specify explicit reference to PNR Lrec.
op values include C-Create, U-Update, D-Delete
2 . 8 7 ( R Q ) P r o f i l e
Elements: Profile
Sub Elements: NameAssociationList; ProfileID; ProfileType; PolicyId; PreferenceId;
PolicyRemovalReason
Profile Attributes: id, op
Profile is used to create the PNR with Profile data.
op values include C-Create, U-Update, D-Delete
ProfileType acceptable values e.g., AGT(TAgent), AGY(TAgency), CRP(CorporateID), TVL(Traveler),
GRP(Group), TVLNN (TvlNoName).
2 . 8 8 ( R Q ) N a m e A s s o c i a t i o n L i s t
Elements: NameAssociationList
Sub Elements: NameAssociationTag; LastName; FirstName; Prefix; NameRefNumber; Id;
ReferenceId
NameAssociationList is used to correlate items being updated with particular passengers.
NameRefNumber reflects how passenger is defined in a PNR structure. NameRefNumber can be substituted by
explicit reference to PNR Lrec via id element.
2 . 8 9 ( R Q ) T i c k e t i n g I n f o
Elements: TicketingInfo
Sub Elements: FutureTicketing; TicketingTimeLimit; AlreadyTicketed
TicketingInfo is used to update PNR with Ticket Details Lrec.
2 . 9 0 ( R Q ) F u t u r e T i c k e t i n g
Elements: FutureTicketing
Sub Elements: Code; CityCode; BranchPCC; QueueCode; Date; Time; QueueNumber; Comment
FutureTicketing Attribute: id, index, op
Sabre Inc. Confidential/All Rights Reserved Request parameters 37
FutureTicketing is used to enter the future date/time details of when the PNR will be ticketed.
op values include C-Create, U-Update, D-Delete
BranchPCC is the pseudo city code of the agent that generated the TK/TE/TR/TV/TM ticketing entry or the
pseudo city code to who the PNR has been queued to perform ticketing.
QueueCode is the queue identification code/pic code.
Date is the date of future ticketing e.g., 18Oct.
Time is the time of future ticketing e.g., 0400A.
2 . 9 1 ( R Q ) T i c k e t i n g T i m e L i m i t
Elements: TicketingTimeLimit
Sub Elements: DownlineCity; CarrierCode; Time; FutureDate; ThirtyMinuteInterval
TicketingTimeLimit
Attribute: id, index, op
TicketingTimeLimit is used to enter the date/time limitation details of when the PNR can be ticketed.
op values include C-Create, U-Update, D-Delete
2 . 9 2 ( R Q ) A l r e a d y T i c k e t e d
Elements: AlreadyTicketed
Sub Elements: Code; Comment
AlreadyTicketed
Attribute: id, index, op
AlreadyTicketed is used to enter ticketing details about the PNR after being ticketed.
op values include C-Create, U-Update, D-Delete
2 . 9 3 ( R Q ) R e m a r k
Elements: Remark
Sub Elements: SegmentAssociationList; RemarkText; OriginalRemarkText
Remark Attributes: id, type, op, code
OriginalRemarkText
Attribute: lang
RemarkUpdate is used to update PNR with Remark Lrec.
Sabre Inc. Confidential/All Rights Reserved Request parameters 38
id attribute can be used to specify explicit reference to PNR Lrec.
op attribute can be used to specify operation type as follows: C=Create, U=Update, D=Delete
type attribute can be used to specify SSR’s category as follows: HS=Historical; HD=Hidden;, CODED = Coded
remark.
2 . 9 4 ( R Q ) S e g m e n t A s s o c i a t i o n L i s t
Elements: SegmentAssociationList
Sub Elements: SegmentAssociationTag; CarrierCode; FlightNumber; DepartureDate; BoardPoint;
OffPoint; ClassOfService; BookingStatus
SegmentAssociationList is used to correlate an item being updated with particular segments.
BoardPoint is used to define departure city.
OffPoint is used to define arrival city.
2 . 9 5 ( R Q ) O t h e r S e r v i c e I n f o r m a t i o n
Elements: OtherServiceInformation
Sub Elements: NameAssociationList; AirlineCode; FreeText
OtherServiceInformation
Attribute: OsiType, id, op
OtherServiceInformation is used to add an OSI record to the PNR.
id attribute can be used to specify explicit reference to PNR Lrec.
op attribute can be used to specify operation type as follows: C=Create, U=Update, D=Delete.
2 . 9 6 ( R Q ) R e c e i v e d F r o m
Elements: ReceivedFrom
Sub Elements: Name; AgentName; TourWholesalerPCC; NewControllingPCC
ReceivedFrom Attribute: fromPassenger
ReceivedFrom is used to identify the person creating the PNR.
Sabre Inc. Confidential/All Rights Reserved Request parameters 39
2 . 9 7 ( R Q ) E m a i l A d d r e s s
Elements: EmailAddress
Sub Elements: NameAssociationList; Address; Comment; OverrideFrom
Address and Comment allow a max of 63 chars.
EmailAddressDataGroup email specifications apply:
A max of 999 emails are allowed in a PNR
You cannot use an underscore character, if one is present it needs to be replaced by two = (e.g.==), this
can only be used before the @ sign
To enter an apostrophe change it to a ?
Max number of chars is 63 in a PNR
The email formats are:
Add email address PE‡(email@address)‡ or PE‡[email protected]‡
Add email address with name select PE‡(email@address)‡-(name ‡), (name ‡) or
PE‡[email protected]‡-1.1.2.1
Add email address with additional data PE‡([email protected])‡(optional entries) or
PE‡[email protected]‡FR/CH AD KIRIBATI
There are several notes in format finder regarding this entry
Create a custom subject line for the email msg:
5V‡SL-(free text) 5V‡SL-YOUR REVISED RESERVATION FOR 18JUN
Free text is limited to one line of 65 chars
Include free text in the email message:
5V‡EM-(free text) 5V‡EM-JUANITA – PLEASE CALL ME AS SOON AS YOU GET THIS EMAIL
Can include up to 3 lines of free text, each line limited to 65 chars
2 . 9 8 ( R Q ) A c c o u n t i n g L i n e
Elements: AccountingLine
Sub Elements:
TypeIndicator; FareApplication; FormOfPaymentCode; LinkCode;
AccountingVendorCode; ChargeCategoryCoded; AirlineDesignator;
DocumentNumber; CommissionPercentage; CommissionAmount; BaseFare;
BasePercent; TaxPercentage; TaxAmount; TaxSurchargeCode2; GSTCode;
CSTAmount; GSTPercent; QSTCode; QSTAmount; QSTPercent;
CreditCardNumber; CreditCardCode; PassengerName;
NumberOfConjunctedDocuments; NumberOfCoupons; OriginalTicketNumber;
OriginalDateOfIssue; OriginalPlaceOfIssue; FullPartialExchangeIndicator;
OriginalInvoice; TarriffBasis; FreeFormText; CurrencyCode; SegmentType;
SegmentNumber
Sabre Inc. Confidential/All Rights Reserved Request parameters 40
AccountingLine
Attributes: id, index, op
AccountingLine is used to add information that is used to produce an invoice for the PNR.
id attribute can be used to specify explicit reference to PNR Lrec.
op attribute can be used to specify operation type as follows: C=Create, U=Update, D=Delete.
index is a number 0 to 99999.
TypeIndicator is the indicator of the accounting line e.g., AC.
FareApplication indicates whom Form of Payment is applied to. Possible values: ONE - a specific passenger,
ALL - all the passengers in the PNR; Per - per person.
FormOfPaymentCode Possible options: CK-check, CA-Cash, CH-Check or cash (trams only), CC-Credit Card,
CX - Credit Card (printed with masking).
ChargeCategoryCoded values include TKT
DocumentNumber number used in conjunction with "ChargeCategoryCode". Document number must contain up
to 7 digits.
CommissionPercentage in range 0-99.
CommissionAmount in range 0-9,999,999.99.
BaseFare amount in range 0-99.
BasePercent base fare percentage in range 0-99.
TaxAmount in range 0-9,999,999.99.
GSTCode goods and services tax or value-added tax code e.g., A,B,C, or D.
GSTAmount goods and services tax or value-added tax amount in range 0-9,999,999.99.
GSTPercent goods and services tax or value-added tax percentage in range 0-99.
QSTCode Quebec Sales Tax code e.g., A,B,C, or D.
QSTAmount Quebec Sales Tax amount in range 0-9,999,999.99.
QSTPercent Quebec Sales Tax percentage in range 0-99.
CreditCardNumber contains up to 16 digits.
CreditCardCode is a two letter code of Credit Card Provider.
PassengerName is used in Form of Payment association (if Fare Application is One), Entry must follow the
pattern: (NameNumber)(Surname)(Given name or initial).
NumberOfConjunctedDocuments is the number of documents the Accounting Line applies to: Amount in range
0-99.
FreeFormText optional text which can contain up to 29 characters.
CurrencyCode Three letter currency code.
SegmentType is the type of segment the Accounting Line is associated to. e.g., "RAL".
SegmentNumber is the number of segment the Accounting Line is associated to.
2 . 9 9 ( R Q ) R e s u l t A c t i o n
Elements: ResultAction
Sub Elements: QueuePlaceAction; QueuePlacement; QueueNumber; CityCode; PitCode
Sabre Inc. Confidential/All Rights Reserved Request parameters 41
QueuePlacement is the QueueNumber and pit code of the queue where the PNR should be placed.
2 . 1 0 0 ( R Q ) C l i e n t C o n t e x t
Element: ClientContext
Sub Elements: Name
This parameter is currently only available with customization.
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 42
3 . 1 S a m p l e R Q , R S i n C r e a t e R e s e r v a t i o n s R Q v 1 . 1 1
3 . 1 . 1 S a m p l e S T L , S t a t e l e s s – a d d R a i l
RQ:
<CreateReservationRQ Version="1.11.0" xmlns="http://webservices.sabre.com/pnrbuilder/v1_11"
xmlns:or="http://services.sabre.com/res/or/v1_4">
<RequestType>Stateless</RequestType>
<ReturnOptions IncludeUpdateDetails="false" RetrievePNR="true">
<ViewName>Full</ViewName>
<ResponseFormat>STL</ResponseFormat>
</ReturnOptions>
<NewReservation>
<Itinerary>
<Product>
<or:ProductDetails>
<or:ProductName type="RAIL">RAL</or:ProductName>
<or:Rail>
<or:StatusCode>GK</or:StatusCode>
<or:Open>false</or:Open>
<or:CrossBorder>false</or:CrossBorder>
<or:Duration>Duration</or:Duration>
<or:MarketingCarrier>
<or:Name>MarketingCarrier-Name</or:Name>
<or:Code codeContext="OTHER">2V</or:Code>
<or:Telephone>
<or:PhoneUseType>MarketingCarrier-
Telephone-PhoneUseType</or:PhoneUseType>
<or:PhoneCountryCode>MarketingCarrier-
Telephone-PhoneCountryCode</or:PhoneCountryCode>
<or:PhoneCountryName>MarketingCarrier-
Telephone-PhoneCountryName</or:PhoneCountryName>
<or:PhoneNumber>MarketingCarrier-
Telephone-PhoneNumber</or:PhoneNumber>
</or:Telephone>
<or:Address>
<or:LocationType>MarketingCarrier-
Address-LocationType</or:LocationType>
<or:AddressLine>MarketingCarrier-
Address-AddressLine</or:AddressLine>
<or:CityName>MarketingCarrier-Address-
CityName</or:CityName>
<or:CityCodes>
<or:Code
codeContext="OTHER">MarketingCarrier-Address-CityCodes-Code</or:Code>
Request and Response payload examples 3
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 43
</or:CityCodes>
<or:LocalCityName>MarketingCarrier-
Address-LocalCityName</or:LocalCityName>
<or:StateProvince code="MarketingCarrier-
Address-StateProvince-code">MarketingCarrier-Address-StateProvince</or:StateProvince>
<or:PostCode>MarketingCarrier-Address-
PostCode</or:PostCode>
<or:Country code="MarketingCarrier-
Address-Country-code">MarketingCarrier-Address-Country</or:Country>
<or:CountryCodes>
<or:Code
codeContext="OTHER">MarketingCarrier-Address-Country-Code</or:Code>
</or:CountryCodes>
<or:Latitude>MarketingCarrier-Address-
Latitude</or:Latitude>
<or:Longitude>MarketingCarrier-Address-
Longitude</or:Longitude>
<or:Altitude>MarketingCarrier-Address-
Altitude</or:Altitude>
</or:Address>
</or:MarketingCarrier>
<or:OperatingCarrier>
<or:Name>PKP</or:Name>
<or:Code codeContext="OTHER"/>
<or:Telephone>
<or:PhoneUseType>OperatingCarrier-
Telephone-PhoneUseType</or:PhoneUseType>
<or:PhoneCountryCode>OperatingCarrier-
Telephone-PhoneCountryCode</or:PhoneCountryCode>
<or:PhoneCountryName>OperatingCarrier-
Telephone-PhoneCountryName</or:PhoneCountryName>
<or:PhoneNumber>OperatingCarrier-
Telephone-PhoneNumber</or:PhoneNumber>
</or:Telephone>
<or:Address>
<or:LocationType>OperatingCarrier-
Address-LocationType</or:LocationType>
<or:AddressLine>OperatingCarrier-
Address-AddressLine</or:AddressLine>
<or:CityName>OperatingCarrier-Address-
CityName</or:CityName>
<or:CityCodes>
<or:Code
codeContext="OTHER">OperatingCarrier-Address-CityCodes-Code</or:Code>
</or:CityCodes>
<or:LocalCityName>OperatingCarrier-
Address-LocalCityName</or:LocalCityName>
<or:StateProvince code="OperatingCarrier-
Address-StateProvince-code">OperatingCarrier-Address-StateProvince</or:StateProvince>
<or:PostCode>OperatingCarrier-Address-
PostCode</or:PostCode>
<or:Country code="OperatingCarrier-
Address-Country-code">OperatingCarrier-Address-Country</or:Country>
<or:CountryCodes>
<or:Code
codeContext="OTHER">OperatingCarrier-Address-Country-Code</or:Code>
</or:CountryCodes>
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 44
<or:Latitude>OperatingCarrier-Address-
Latitude</or:Latitude>
<or:Longitude>OperatingCarrier-Address-
Longitude</or:Longitude>
<or:Altitude>OperatingCarrier-Address-
Altitude</or:Altitude>
</or:Address>
</or:OperatingCarrier>
<or:Passengers quantity="5">
<or:Passenger passengerID="" primary="true">
<or:Type code="ADT"
codeContext="OTHER">ADT</or:Type>
<or:PersonName>
<or:Prefix>Passengers-Passenger-
PersonName-Prefix</or:Prefix>
<or:Given>Passengers-Passenger-
PersonName-Given</or:Given>
<or:Middle>Passengers-Passenger-
PersonName-Middle</or:Middle>
<or:Surname>Passengers-
Passenger-PersonName-Surname</or:Surname>
<or:Suffix>Maiden</or:Suffix>
<or:Type>Nickname</or:Type>
<or:PreferredFirstName>Passengers-Passenger-PersonName-PreferredFirstName</or:PreferredFirstName>
<or:PreferredSurname>Passengers-
Passenger-PersonName-PreferredSurname</or:PreferredSurname>
</or:PersonName>
<or:Telephone>
<or:PhoneUseType>Passengers-
Passenger-Telephone-PhoneUseType</or:PhoneUseType>
<or:PhoneCountryCode>Passengers-Passenger-Telephone-PhoneCountryCode</or:PhoneCountryCode>
<or:PhoneCountryName>Passengers-Passenger-Telephone-PhoneCountryName</or:PhoneCountryName>
<or:PhoneNumber>Passengers-
Passenger-Telephone-PhoneNumber</or:PhoneNumber>
</or:Telephone>
<or:Email>Passengers-Passenger-
Email</or:Email>
</or:Passenger>
</or:Passengers>
<or:SupplementaryServices>
<or:SupplementaryService
type="SupplementaryServices-SupplementaryService-type" code="SupplementaryServices-SupplementaryService-
code" codeContext="OTHER">
<or:Description
lang="en">SupplementaryServices-SupplementaryService-Description</or:Description>
<or:Charges>
<or:GeneralNotes>SupplementaryServices-SupplementaryService-Charges-
GeneralNotes</or:GeneralNotes>
<or:Charge
currencyCode="SupplementaryServices-SupplementaryService-Charges-Charge-currencyCode">
<or:Description>SupplementaryServices-SupplementaryService-Charges-Charge-
Description</or:Description>
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 45
<or:Notes>SupplementaryServices-SupplementaryService-Charges-Charge-Notes</or:Notes>
<or:Name>SupplementaryServices-SupplementaryService-Charges-Charge-Name</or:Name>
<or:Calculation>
<or:UnitName>SupplementaryServices-SupplementaryService-Charges-Charge-Calculation-
UnitName</or:UnitName>
<or:UnitCharge
min="10.01" max="1000.01">111.11</or:UnitCharge>
<or:Quantity
min="11.01" max="1001.01">22.22</or:Quantity>
<or:Total
min="12.02" max="1002.02">333.33</or:Total>
</or:Calculation>
<or:BillingType>SupplementaryServices-SupplementaryService-Charges-Charge-
BillingType</or:BillingType>
</or:Charge>
<or:GrandTotal
currencyCode="SupplementaryServices-SupplementaryService-Charges-GrandTotal-
currencyCode">444.44</or:GrandTotal>
<or:GeneralBillingType>SupplementaryServices-SupplementaryService-Charges-Charge-
GeneralBillingType</or:GeneralBillingType>
</or:Charges>
<or:PassengerReferences>
<or:PassengerRef id="1"/>
</or:PassengerReferences>
</or:SupplementaryService>
</or:SupplementaryServices>
<or:TrainInfo>
<or:Number>SOBIESKI 33</or:Number>
<or:Code>TrainInfo-Code</or:Code>
<or:ShortName>TrainInfo-
ShortName</or:ShortName>
<or:LongName>TrainInfo-
LongName</or:LongName>
</or:TrainInfo>
<or:Accommodation>
<or:PassengerRef>Accommodation-
PassengerRef</or:PassengerRef>
<or:Placement code="Accommodation-Placement-
code" type="TABORET">
<or:Coach>
<or:CoachNumber>CN44</or:CoachNumber>
<or:PlacementNumber
compartmentRefId="Accommodation-Placement-Coach-PlacementNumber-
compartmentRefId">PN33</or:PlacementNumber>
<or:CompartmentNumber>Accommodation-Placement-Coach-
CompartmentNumber</or:CompartmentNumber>
</or:Coach>
<or:Detail>Accommodation-Placement-
Detail</or:Detail>
</or:Placement>
<or:Meal>Accommodation-Meal</or:Meal>
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 46
</or:Accommodation>
<or:StartDetails>
<or:Address>
<or:LocationType>StartDetails-Address-
LocationType</or:LocationType>
<or:AddressLine>StartDetails-Address-
AddressLine</or:AddressLine>
<or:CityName>PARIS</or:CityName>
<or:CityCodes>
<or:Code
codeContext="OTHER">PARISGAREDEL</or:Code>
</or:CityCodes>
<or:LocalCityName>StartDetails-Address-
LocalCityName</or:LocalCityName>
<or:StateProvince code="StartDetails-
Address-StateProvince-code">StartDetails-Address-StateProvince</or:StateProvince>
<or:PostCode>StartDetails-Address-
PostCode</or:PostCode>
<or:Country code="StartDetails-Address-
Country-code">StartDetails-Address-Country</or:Country>
<or:CountryCodes>
<or:Code
codeContext="OTHER">StartDetails-Address-Country-Code</or:Code>
</or:CountryCodes>
<or:Latitude>StartDetails-Address-
Latitude</or:Latitude>
<or:Longitude>StartDetails-Address-
Longitude</or:Longitude>
<or:Altitude>StartDetails-Address-
Altitude</or:Altitude>
</or:Address>
<or:DateTime>2021-01-10T13:11:00</or:DateTime>
<or:AirportInfo>
<or:Airline code="StartDetails-AirportInfo-
Airline-code" flightNumber="1111" flightDateTime="2011-01-10T01:11:11" flightType="D"
privateAviation="true">StartDetails-AirportInfo-Airline</or:Airline>
<or:AirportName>PAR</or:AirportName>
<or:LocationCode>DN</or:LocationCode>
<or:Terminal>StartDetails-AirportInfo-
Terminal</or:Terminal>
<or:Gate>StartDetails-AirportInfo-
Gate</or:Gate>
</or:AirportInfo>
<or:Comments>StartDetails-
Comments</or:Comments>
</or:StartDetails>
<or:StopDetails>
<or:Address>
<or:LocationType>StopDetails-Address-
LocationType</or:LocationType>
<or:AddressLine>StopDetails-Address-
AddressLine</or:AddressLine>
<or:CityName>MARSEILLE</or:CityName>
<or:CityCodes>
<or:Code
codeContext="OTHER">MARSEILLESAINT</or:Code>
</or:CityCodes>
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 47
<or:LocalCityName>StopDetails-Address-
LocalCityName</or:LocalCityName>
<or:StateProvince code="StopDetails-
Address-StateProvince-code">StopDetails-Address-StateProvince</or:StateProvince>
<or:PostCode>StopDetails-Address-
PostCode</or:PostCode>
<or:Country code="StopDetails-Address-
Country-code">StopDetails-Address-Country</or:Country>
<or:CountryCodes>
<or:Code
codeContext="OTHER">StopDetails-Address-Country-Code</or:Code>
</or:CountryCodes>
<or:Latitude>StopDetails-Address-
Latitude</or:Latitude>
<or:Longitude>StopDetails-Address-
Longitude</or:Longitude>
<or:Altitude>StopDetails-Address-
Altitude</or:Altitude>
</or:Address>
<or:DateTime>2021-01-10T01:11:11</or:DateTime>
<or:AirportInfo>
<or:Airline code="StopDetails-AirportInfo-
Airline-code" flightNumber="1111" flightDateTime="2011-01-10T01:11:11" flightType="D"
privateAviation="true">StopDetails-AirportInfo-Airline</or:Airline>
<or:AirportName>LON</or:AirportName>
<or:LocationCode>DN</or:LocationCode>
<or:Terminal>StopDetails-AirportInfo-
Terminal</or:Terminal>
<or:Gate>StopDetails-AirportInfo-
Gate</or:Gate>
</or:AirportInfo>
<or:Comments>StopDetails-
Comments</or:Comments>
</or:StopDetails>
<or:EndDetails>
<or:Address>
<or:LocationType>EndDetails-Address-
LocationType</or:LocationType>
<or:AddressLine>EndDetails-Address-
AddressLine</or:AddressLine>
<or:CityName>MARSEILLE</or:CityName>
<or:CityCodes>
<or:Code
codeContext="OTHER">MARSEILLESAINT</or:Code>
</or:CityCodes>
<or:LocalCityName>EndDetails-Address-
LocalCityName</or:LocalCityName>
<or:StateProvince code="EndDetails-
Address-StateProvince-code">EndDetails-Address-StateProvince</or:StateProvince>
<or:PostCode>EndDetails-Address-
PostCode</or:PostCode>
<or:Country code="EndDetails-Address-
Country-code">EndDetails-Address-Country</or:Country>
<or:CountryCodes>
<or:Code
codeContext="OTHER">EndDetails-Address-Country-Code</or:Code>
</or:CountryCodes>
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 48
<or:Latitude>EndDetails-Address-
Latitude</or:Latitude>
<or:Longitude>EndDetails-Address-
Longitude</or:Longitude>
<or:Altitude>EndDetails-Address-
Altitude</or:Altitude>
</or:Address>
<or:DateTime>2016-01-11T02:23:00</or:DateTime>
<or:AirportInfo>
<or:Airline code="EndDetails-AirportInfo-
Airline-code" flightNumber="1111" flightDateTime="2011-01-10T01:11:11" flightType="D"
privateAviation="true">EndDetails-AirportInfo-Airline</or:Airline>
<or:AirportName>LON</or:AirportName>
<or:LocationCode>DN</or:LocationCode>
<or:Terminal>EndDetails-AirportInfo-
Terminal</or:Terminal>
<or:Gate>EndDetails-AirportInfo-
Gate</or:Gate>
</or:AirportInfo>
<or:Comments>EndDetails-
Comments</or:Comments>
</or:EndDetails>
<or:RailFares>
<or:Fare>
<or:PassengerReferences>
<or:PassengerRef id="RailFares-
Fare-PassengerReferences-PassengerRef-id"/>
</or:PassengerReferences>
<or:SegmentReferences>
<or:SegmentRef id="RailFares-
Fare-SegmentReferences-SegmentRef-id"/>
</or:SegmentReferences>
<or:ClassOfService code="RailFares-Fare-
ClassOfService-code" type="RailFares-Fare-ClassOfService-type">RailFares-Fare-
ClassOfService</or:ClassOfService>
<or:ClassCode code="RailFares-Fare-
ClassCode-code" type="RailFares-Fare-ClassCode-type">RailFares-Fare-ClassCode</or:ClassCode>
<or:FareDescription>
<or:Name>RailFares-Fare-
FareDescription-Name</or:Name>
<or:Code>RailFares-Fare-
FareDescription-Code</or:Code>
<or:Detail type="RailFares-Fare-
FareDescription-Detail-type" codeContext="RailFares-Fare-FareDescription-Detail-codeContext">RailFares-Fare-
FareDescription-Detail</or:Detail>
<or:Condition
lang="en">RailFares-Fare-FareDescription-Condition</or:Condition>
<or:Fees>
<or:Fee name="RailFares-
Fare-FareDescription-Fees-Fee-name" type="RailFares-Fare-FareDescription-Fees-Fee-type"
currencyCode="RailFares-Fare-FareDescription-Fees-Fee-currencyCode">
<or:Amount>RailFares-Fare-FareDescription-Fees-Fee-Amount</or:Amount>
<or:Description>RailFares-Fare-FareDescription-Fees-Fee-Description</or:Description>
</or:Fee>
</or:Fees>
</or:FareDescription>
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 49
<or:FarePrice currencyCode="RailFares-
Fare-FarePrice-currencyCode">444.44</or:FarePrice>
</or:Fare>
</or:RailFares>
<or:Documents>
<or:Document type="Documents-Document-
DocumentID-type" code="Documents-Document-DocumentID-code" codeContext="OTHER">
<or:DocumentID>Documents-Document-
DocumentID</or:DocumentID>
<or:AgencyAccountNumber>Documents-
Document-AgencyAccountNumber</or:AgencyAccountNumber>
<or:CreationChannel>Documents-
Document-CreationChannel</or:CreationChannel>
<or:PassengerReferences>
<or:PassengerRef id="Documents-
Document-PassengerReferences-PassengerRef-id"/>
</or:PassengerReferences>
<or:SegmentReferences>
<or:SegmentRef id="Document-
SegmentReferences-SegmentRef-id"/>
</or:SegmentReferences>
<or:IssueTimeLimit>2011-01-
10T01:11:11</or:IssueTimeLimit>
<or:IssueDateTime>2011-01-
10T01:11:11</or:IssueDateTime>
<or:DocumentStatus>HGW</or:DocumentStatus>
<or:Charges>
<or:GeneralNotes>Documents-
Document-Charges-GeneralNotes</or:GeneralNotes>
<or:Charge
currencyCode="Documents-Document-Charges-Charge-currencyCode">
<or:Description>Documents-Document-Charges-Charge-Description</or:Description>
<or:Notes>Documents-
Document-Charges-Charge-Notes</or:Notes>
<or:Name>Documents-
Document-Charges-Charge-Name</or:Name>
<or:Calculation>
<or:UnitName>Documents-Document-Charges-Charge-Calculation-UnitName</or:UnitName>
<or:UnitCharge
min="10.01" max="1000.01">111.11</or:UnitCharge>
<or:Quantity
min="11.01" max="1001.01">22.22</or:Quantity>
<or:Total
min="12.02" max="1002.02">333.33</or:Total>
</or:Calculation>
<or:BillingType>Documents-Document-Charges-Charge-BillingType</or:BillingType>
</or:Charge>
<or:GrandTotal
currencyCode="Documents-Document-Charges-GrandTotal-currencyCode">444.44</or:GrandTotal>
<or:GeneralBillingType>Documents-Document-Charges-Charge-
GeneralBillingType</or:GeneralBillingType>
</or:Charges>
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 50
<or:FormOfPayment
transactionID="Documents-Document-FormOfPayment-transactionID">
<or:Cash>Documents-Document-
FormOfPayment-Cash</or:Cash>
<or:Check>Documents-Document-
FormOfPayment-Check</or:Check>
<or:Voucher>Documents-
Document-FormOfPayment-Voucher</or:Voucher>
<or:Other>Documents-Document-
FormOfPayment-Other</or:Other>
</or:FormOfPayment>
<or:File type="Documents-Document-File-
type" coding="Documents-Document-File-coding">
<or:Representation>Documents-
Document-File-Representation</or:Representation>
<or:URL>Documents-Document-
File-URL</or:URL>
</or:File>
<or:IssueType>Documents-Document-
IssueType</or:IssueType>
<or:DocumentRules>
<or:Exchangable>Documents-
Document-DocumentRules-Exchangable</or:Exchangable>
<or:Refundable>Documents-
Document-DocumentRules-Refundable</or:Refundable>
<or:Rule type="Documents-
Document-DocumentRules-Rule-type">Documents-Document-DocumentRules-Rule</or:Rule>
</or:DocumentRules>
</or:Document>
</or:Documents>
<or:Details>
<or:Detail type="A">Details-Detail</or:Detail>
</or:Details>
</or:Rail>
</or:ProductDetails>
</Product>
</Itinerary>
<PersonName>
<Given>JOHN</Given>
<Surname>DEPP</Surname>
</PersonName>
<PhoneNumber id="1">
<PhoneText>1122334455</PhoneText>
</PhoneNumber>
<DkNumber>1234567</DkNumber>
<TicketingInfo>
<AlreadyTicketed id="1">
<Code>T-A</Code>
<Comment/>
</AlreadyTicketed>
</TicketingInfo>
<ReceivedFrom>
<Name>TDS_QA</Name>
</ReceivedFrom>
</NewReservation>
<ResultAction/>
</CreateReservationRQ>
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 51
RS:
<CreateReservationRS xmlns="http://webservices.sabre.com/pnrbuilder/v1_11"
xmlns:ns2="http://services.sabre.com/res/or/v1_4" xmlns:ns3="http://tds.sabre.com/itinerary">
<Success>OK</Success>
<Locator>HOYJCQ</Locator>
<Errors/>
<Reservation numberInParty="1" numberOfInfants="0" NumberInSegment="1">
<BookingDetails>
<RecordLocator>HOYJCQ</RecordLocator>
<CreationTimestamp>2015-06-12T10:21:00</CreationTimestamp>
<SystemCreationTimestamp>2015-06-12T10:21:00</SystemCreationTimestamp>
<CreationAgentID>BMR</CreationAgentID>
<UpdateTimestamp>2015-06-12T10:21:01</UpdateTimestamp>
<PNRSequence>1</PNRSequence>
<DivideSplitDetails/>
<UpdateToken>7a74122b810421423300b4e66b986cd89d187448fb18d85d</UpdateToken>
</BookingDetails>
<POS>
<Source BookingSource="M9N4" AgentSine="BMR" PseudoCityCode="M9N4" ISOCountry="US"
AgentDutyCode="*" AirlineVendorID="AA"/>
</POS>
<PassengerReservation>
<Passengers>
<Passenger id="4" nameType="S" passengerType="ADT" nameId="01.01" nameAssocId="1">
<LastName>DEPP</LastName>
<FirstName>JOHN</FirstName>
<Seats/>
</Passenger>
</Passengers>
<Segments>
<Segment sequence="1" id="3">
<General isPast="false">
<Line Number="1" Type="RAL" Status="GK"/>
<Vendor Code="2V"/>
<NumberInParty>5</NumberInParty>
<OriginLocation LocationCode="PARIS" Point="PAR-DN"/>
<DestinationLocation LocationCode="MARSEILLE" Point="LON-DN"/>
<DateTime>2021-01-10T13:11:00</DateTime>
<ArrivalDateTime>2016-01-11T02:23:00</ArrivalDateTime>
<ServiceInformation>HGW</ServiceInformation>
<SpaceReserved>TABORET PN33-CN44</SpaceReserved>
<ShipOrVehicleName>SOBIESKI 33</ShipOrVehicleName>
<Text>LV-1311/FR-PAR-DN/DT-11JAN/AR-0223/AT-LON-DN/NA-SOBIESKI 33/SP-
TABORET PN33-CN44/SI-HGW</Text>
</General>
</Segment>
</Segments>
<TicketingInfo>
<AlreadyTicketed id="8" index="1">
<Code>T-A</Code>
</AlreadyTicketed>
</TicketingInfo>
<ItineraryPricing/>
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 52
</PassengerReservation>
<DKNumbers>
<DKNumber>1234567</DKNumber>
</DKNumbers>
<ReceivedFrom>
<Name>TDS_QA</Name>
</ReceivedFrom>
<PhoneNumbers>
<PhoneNumber id="6" index="1">
<CityCode>DFW</CityCode>
<Number>1122334455</Number>
</PhoneNumber>
</PhoneNumbers>
<EmailAddresses/>
<History>
<HistoryTransaction>
<Signature SequenceNbr="1">
<HistoryTimestamp>2015-06-12T10:21:00</HistoryTimestamp>
<DutyCode>*</DutyCode>
<AgentSine>BMR</AgentSine>
<HomePCC>HDQ</HomePCC>
<AgencyPCC>M9N4</AgencyPCC>
<HistoryFrom>TDS_QA</HistoryFrom>
</Signature>
<ItineraryHistory>
<GeneralSegment>
<HistoryAction>AS</HistoryAction>
<VendorCode>2V</VendorCode>
<DateTime>2021-01-10T00:00:00</DateTime>
<Text>PARIS MARSEILLE/LV-1311/FR-PAR-DN/DT-11JAN/AR-0223/AT-LON-DN/NA-
SOBIESKI 33/SP-TABORET PN33-CN44/SI-HGW</Text>
</GeneralSegment>
</ItineraryHistory>
<TicketingHistory>
<OriginalTicketDetails>T-A</OriginalTicketDetails>
<TransactionIndicator>T</TransactionIndicator>
<AgencyLocation/>
<HistoryAction>A7</HistoryAction>
</TicketingHistory>
<NameHistory>
<HistoryAction>AN</HistoryAction>
<NameSeqID>1</NameSeqID>
<LastName>DEPP</LastName>
<FirstName>JOHN</FirstName>
</NameHistory>
<PhoneHistory>
<Location>O</Location>
<TJRCityCode>DFW</TJRCityCode>
<CityCode/>
<Extension/>
<Number>1122334455</Number>
<HistoryAction>A9</HistoryAction>
</PhoneHistory>
<PassengerDetailsHistory>
<HistoryAction>ADT</HistoryAction>
<NameID>1</NameID>
<PassengerDetailType></PassengerDetailType>
<PassengerDetails>
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 53
<PassengerType>
<PassengerType>ADT</PassengerType>
</PassengerType>
</PassengerDetails>
</PassengerDetailsHistory>
</HistoryTransaction>
</History>
</Reservation>
</CreateReservationRS>
3 . 1 . 2 S a m p l e S T L , S t a t e l e s s – T o u r p a c k a g e
RQ:
<CreateReservationRQ Version="1.11.0" xmlns="http://webservices.sabre.com/pnrbuilder/v1_11"
xmlns:or="http://services.sabre.com/res/or/v1_4">
<RequestType>Stateless</RequestType>
<ReturnOptions IncludeUpdateDetails="false" RetrievePNR="true">
<ViewName>Default</ViewName>
<ResponseFormat>STL</ResponseFormat>
</ReturnOptions>
<NewReservation>
<Itinerary>
<Product>
<or:ProductBase>
<or:ProductType>TOR</or:ProductType>
<or:VendorCode>XY</or:VendorCode>
<or:StatusCode>HK</or:StatusCode>
<or:StartPoint>KRK</or:StartPoint>
<or:StartDateTime>2015-05-30T00:00:00</or:StartDateTime>
<or:EndPoint>WAW</or:EndPoint>
<or:EndDateTime>2015-06-15T00:00:00</or:EndDateTime>
<or:Text>Text</or:Text>
</or:ProductBase>
<or:ProductDetails>
<or:ProductName type="TOUR"/>
<or:Tour>
<or:StatusCode>GK</or:StatusCode>
<or:MessageStatus>messageStatus</or:MessageStatus>
<or:TravelType>travelType</or:TravelType>
<or:Vendor>
<or:Name>VendorName</or:Name>
<or:Code
codeContext="VendorCodeContext">VendorCode</or:Code>
<or:Telephone>
<or:PhoneUseType>VendorPhoneUseType</or:PhoneUseType>
<or:PhoneCountryCode>48</or:PhoneCountryCode>
<or:PhoneCountryName>VendorPhoneCountryName</or:PhoneCountryName>
<or:PhoneNumber>1234567890</or:PhoneNumber>
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 54
</or:Telephone>
<or:Address>
<or:LocationType>VendorAddressLocationType</or:LocationType>
<or:AddressLine>VendorAddressLine</or:AddressLine>
<or:CityName>VendorAddressCityName</or:CityName>
<or:CityCodes>
<or:Code
codeContext="VendorAddressCityContextCode">VendorAddressCityCode</or:Code>
</or:CityCodes>
<or:LocalCityName>VendorAddressLocalCityName</or:LocalCityName>
<or:StateProvince>VendorAddressStateProvince</or:StateProvince>
<or:StateProvinceCodes>
<or:Code
codeContext="VendorAddressStateProvince">VendorAddressStateProvince</or:Code>
</or:StateProvinceCodes>
<or:PostCode>VendorAddressPostCode</or:PostCode>
<or:Country>VendorAddressCountry</or:Country>
<or:CountryCodes>
<or:Code
codeContext="VendorAddressCountryContextCode">VendorAddressCountryCode</or:Code>
</or:CountryCodes>
<or:Latitude>VendorAddressLatitude</or:Latitude>
<or:Longitude>VendorAddressLongitude</or:Longitude>
<or:Altitude>VendorAddressAltitude</or:Altitude>
</or:Address>
</or:Vendor>
<or:StartDetails>
<or:Address>
<or:LocationType>StartDetailsAddressLocationType</or:LocationType>
<or:AddressLine>StartDetailsAddressAddressLine</or:AddressLine>
<or:CityName>StartDetailsAddressCityName</or:CityName>
<or:CityCodes>
<or:Code
codeContext="StartDetailsAddressCityCodeContext">StartDetailsAddressCityCode</or:Code>
</or:CityCodes>
<or:LocalCityName>StartDetailsAddressLocalCityName</or:LocalCityName>
<or:StateProvince
code="StartDetailsAddressStateProvinceCodeContext">StartDetailsAddressStateProvince</or:StateProvince>
<or:StateProvinceCodes>
<or:Code
codeContext="StartDetailsAddressStateProvinceCodeContext">StartDetailsAddressStateProvinceCode</or:Code>
</or:StateProvinceCodes>
<or:PostCode>StartDetailsAddressPostCode</or:PostCode>
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 55
<or:Country
code="StartDetailsAddressCountryCode">StartDetailsAddressCountry</or:Country>
<or:Latitude>StartDetailsAddressLatitude</or:Latitude>
<or:Longitude>StartDetailsAddressLongitude</or:Longitude>
<or:Altitude>StartDetailsAddressAltitude</or:Altitude>
</or:Address>
<or:DateTime>2015-09-30T00:00:00</or:DateTime>
<or:AirportInfo>
<or:Airline code="WS"
flightNumber="123" flightDateTime="2015-05-30T00:00:00" flightType="A"
privateAviation="true">N</or:Airline>
<or:AirportName>StartDetailsAirportInfoAirportName</or:AirportName>
<or:LocationCode>StartDetailsAirportInfoLocationCode</or:LocationCode>
<or:Terminal>StartDetailsAirportInfoTerminal</or:Terminal>
<or:Gate>StartDetailsAirportInfoGate</or:Gate>
</or:AirportInfo>
<or:Comments>StartDetailsComments</or:Comments>
</or:StartDetails>
<or:EndDetails>
<or:Address>
<or:LocationType>EndDetailsAddressLocationType</or:LocationType>
<or:AddressLine>EndDetailsAddressAddressLine</or:AddressLine>
<or:CityName>EndDetailsAddressCityName</or:CityName>
<or:CityCodes>
<or:Code
codeContext="EndDetailsAddressCityCodeContext">EndDetailsAddressCityCode</or:Code>
</or:CityCodes>
<or:LocalCityName>EndDetailsAddressLocalCityName</or:LocalCityName>
<or:StateProvince
code="EndDetailsAddressStateProvinceCode">EndDetailsAddressStateProvince</or:StateProvince>
<or:StateProvinceCodes>
<or:Code
codeContext="EndDetailsAddressStateProvinceCodeContext">EndDetailsAddressStateProvinceCode</or:Code>
</or:StateProvinceCodes>
<or:PostCode>EndDetailsAddressPostCode</or:PostCode>
<or:Country
code="EndDetailsAddressCountryCode">EndDetailsAddressCountry</or:Country>
<or:Latitude>EndDetailsAddressLatitude</or:Latitude>
<or:Longitude>EndDetailsAddressLongitude</or:Longitude>
<or:Altitude>EndDetailsAddressAltitude</or:Altitude>
</or:Address>
<or:DateTime>2015-05-30T00:00:00</or:DateTime>
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 56
<or:AirportInfo>
<or:Airline
code="EndDetailsAirportInfoAirlineCode" flightNumber="123" flightDateTime="2015-05-30T00:00:00"
flightType="A" privateAviation="true">N</or:Airline>
<or:AirportName>EndDetailsAirportInfoAirportName</or:AirportName>
<or:LocationCode>EndDetailsAirportInfoLocationCode</or:LocationCode>
<or:Terminal>EndDetailsAirportInfoTerminal</or:Terminal>
<or:Gate>EndDetailsAirportInfoGate</or:Gate>
</or:AirportInfo>
<or:Comments>EndDetailsComments</or:Comments>
</or:EndDetails>
<or:Price>
<or:Total
currencyCode="PriceTotalCurrencyCode">100</or:Total>
<or:Breakdown>
<or:References>
<or:PassengerRef id="1"/>
</or:References>
<or:Price
currencyCode="PLN">100</or:Price>
</or:Breakdown>
</or:Price>
<or:Customer>
<or:Type code="CustomerTypeCode"
codeContext="CustomerCodeContext"/>
<or:PersonName>
<or:Prefix>CustomerPersonNamePrefix</or:Prefix>
<or:Given>CustomerPersonNameGiven</or:Given>
<or:Middle>CustomerPersonNameMiddle</or:Middle>
<or:Surname>CustomerPersonNameSurname</or:Surname>
<or:Suffix>CustomerPersonNameSuffix</or:Suffix>
<or:Type>CustomerPersonNameType</or:Type>
<or:PreferredFirstName>CustomerPersonNamePreferredFirstName</or:PreferredFirstName>
<or:PreferredSurname>CustomerPersonNamePreferredSurname</or:PreferredSurname>
</or:PersonName>
<or:Telephone>
<or:PhoneUseType>CustomerTelephonePhoneUseType</or:PhoneUseType>
<or:PhoneCountryCode>48</or:PhoneCountryCode>
<or:PhoneCountryName>CustomerTelephonePhoneCountryName</or:PhoneCountryName>
<or:PhoneNumber>123456</or:PhoneNumber>
</or:Telephone>
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 57
<or:Email>CustomerEmail</or:Email>
<or:Address>
<or:LocationType>CustomerAddressLocationType</or:LocationType>
<or:AddressLine>CustomerAddressAddressLine</or:AddressLine>
<or:CityName>CustomerAddressCityName</or:CityName>
<or:CityCodes>
<or:Code
codeContext="CustomerAddressCityCodeContext">CustomerAddressCityCode</or:Code>
</or:CityCodes>
<or:LocalCityName>CustomerAddressLocalCityName</or:LocalCityName>
<or:StateProvince
code="CustomerAddressStateProvinceCode">CustomerAddressStateProvince</or:StateProvince>
<or:StateProvinceCodes>
<or:Code
codeContext="CustomerAddressStateProvinceContextCode">CustomerAddressStateProvinceCode</or:Code>
</or:StateProvinceCodes>
<or:PostCode>CustomerAddressPostCode</or:PostCode>
<or:Country
code="CustomerAddressCountryCode">CustomerAddressCountry</or:Country>
<or:CountryCodes>
<or:Code
codeContext="CustomerAddressCountryCodeContext">CustomerAddressCountryCode</or:Code>
</or:CountryCodes>
<or:Latitude>CustomerAddressLatitude</or:Latitude>
<or:Longitude>CustomerAddressLongitude</or:Longitude>
<or:Altitude>CustomerAddressAltitude</or:Altitude>
</or:Address>
<or:Age>50</or:Age>
</or:Customer>
<or:Services>
<or:Service>
<or:Description
lang="EN">ServiceDescription</or:Description>
<or:PassengerReferences>
<or:PassengerRef id="1"/>
</or:PassengerReferences>
<or:Accommodation>ServiceAccommodation</or:Accommodation>
<or:Occupancy>ServiceOccupancy</or:Occupancy>
<or:NoOfServices>1</or:NoOfServices>
<or:TravellerAllocation>ServiceTravellerAllocation</or:TravellerAllocation>
<or:ServicePrice
currencyCode="PLN">10.00</or:ServicePrice>
<or:StealBoarding>ServiceStealBoarding</or:StealBoarding>
</or:Service>
</or:Services>
</or:Tour>
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 58
</or:ProductDetails>
<or:AdditionalContent persist="true" name="Other">
<or:ParametersMap>
<or:entry>
<or:key>Vendor</or:key>
<or:value>AA</or:value>
</or:entry>
</or:ParametersMap>
</or:AdditionalContent>
<or:AdditionalContent persist="true" name="TOURSegment">
<or:ParametersMap>
<or:entry>
<or:key>Vendor</or:key>
<or:value>7T</or:value>
</or:entry>
<or:entry>
<or:key>NumberOfPeople</or:key>
<or:value>2</or:value>
</or:entry>
<or:entry>
<or:key>CityCode</or:key>
<or:value>KRK</or:value>
</or:entry>
<or:entry>
<or:key>Date</or:key>
<or:value>2021-01-20T14:12:00</or:value>
</or:entry>
<or:entry>
<or:key>TouroperatorName</or:key>
<or:value>AMERICAN EXPRESS</or:value>
</or:entry>
<or:entry>
<or:key>RoomType</or:key>
<or:value>DBLB</or:value>
</or:entry>
<or:entry>
<or:key>N</or:key>
<or:value>5</or:value>
</or:entry>
<or:entry>
<or:key>SI</or:key>
<or:value>AAAABBBBCCCC</or:value>
</or:entry>
</or:ParametersMap>
</or:AdditionalContent>
</Product>
</Itinerary>
<PersonName>
<Given>JOHN</Given>
<Surname>DEPP</Surname>
</PersonName>
<PhoneNumber id="1">
<PhoneText>1122334455</PhoneText>
</PhoneNumber>
<DkNumber>1234567</DkNumber>
<TicketingInfo>
<AlreadyTicketed id="1">
<Code>T-A</Code>
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 59
<Comment/>
</AlreadyTicketed>
</TicketingInfo>
<ReceivedFrom>
<Name>TDS_QA</Name>
</ReceivedFrom>
</NewReservation>
<ResultAction/>
</CreateReservationRQ>
RS:
<CreateReservationRS xmlns="http://webservices.sabre.com/pnrbuilder/v1_11"
xmlns:ns2="http://services.sabre.com/res/or/v1_4" xmlns:ns3="http://tds.sabre.com/itinerary">
<Success>OK</Success>
<Locator>HOZMHW</Locator>
<Errors/>
<Reservation numberInParty="1" numberOfInfants="0" NumberInSegment="1">
<BookingDetails>
<RecordLocator>HOZMHW</RecordLocator>
<CreationTimestamp>2015-06-12T10:24:00</CreationTimestamp>
<SystemCreationTimestamp>2015-06-12T10:24:00</SystemCreationTimestamp>
<CreationAgentID>BMR</CreationAgentID>
<UpdateTimestamp>2015-06-12T10:24:44</UpdateTimestamp>
<PNRSequence>1</PNRSequence>
<DivideSplitDetails/>
<UpdateToken>7a74122b8104214211dd6b5cc4c48dc35af85257709fdf73</UpdateToken>
</BookingDetails>
<POS>
<Source BookingSource="M9N4" AgentSine="BMR" PseudoCityCode="M9N4" ISOCountry="US"
AgentDutyCode="*" AirlineVendorID="AA"/>
</POS>
<PassengerReservation>
<Passengers>
<Passenger id="4" nameType="S" passengerType="ADT" nameId="01.01" nameAssocId="1">
<LastName>DEPP</LastName>
<FirstName>JOHN</FirstName>
<Seats/>
</Passenger>
</Passengers>
<Segments>
<Segment sequence="1" id="3">
<General isPast="false">
<Line Number="1" Type="TOR" Status="GK"/>
<Vendor Code="7T"/>
<NumberInParty>2</NumberInParty>
<Location LocationCode="KRK"/>
<DateTime>2021-01-20T00:00:00</DateTime>
<ServiceInformation>AAAABBBBCCCC</ServiceInformation>
<Tour>
<Name>AMERICAN EXPRESS</Name>
<NumberOfNights>5</NumberOfNights>
<RoomType>DBLB</RoomType>
</Tour>
<Text>AMERICAN EXPRESS/DBLB/N-5/SI-AAAABBBBCCCC</Text>
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 60
</General>
</Segment>
</Segments>
<TicketingInfo>
<AlreadyTicketed id="8" index="1">
<Code>T-A</Code>
</AlreadyTicketed>
</TicketingInfo>
<ItineraryPricing/>
</PassengerReservation>
<DKNumbers>
<DKNumber>1234567</DKNumber>
</DKNumbers>
<ReceivedFrom>
<Name>TDS_QA</Name>
</ReceivedFrom>
<PhoneNumbers>
<PhoneNumber id="6" index="1">
<CityCode>DFW</CityCode>
<Number>1122334455</Number>
</PhoneNumber>
</PhoneNumbers>
<EmailAddresses/>
</Reservation>
</CreateReservationRS>
3 . 1 . 3 S a m p l e S T L , S t a t e f u l – a d d R a i l
RQ:
<CreateReservationRQ Version="1.11.0" xmlns="http://webservices.sabre.com/pnrbuilder/v1_11"
xmlns:or="http://services.sabre.com/res/or/v1_4">
<RequestType>Stateful</RequestType>
<ReturnOptions IncludeUpdateDetails="false" RetrievePNR="true">
<ViewName>Default</ViewName>
<ResponseFormat>STL</ResponseFormat>
</ReturnOptions>
<NewReservation>
<Itinerary>
<Product>
<or:ProductDetails>
<or:ProductName type="RAIL">RAL</or:ProductName>
<or:Rail>
<or:StatusCode>GK</or:StatusCode>
<or:Open>false</or:Open>
<or:CrossBorder>false</or:CrossBorder>
<or:Duration>Duration</or:Duration>
<or:MarketingCarrier>
<or:Name>MarketingCarrier-Name</or:Name>
<or:Code codeContext="OTHER">2V</or:Code>
<or:Telephone>
<or:PhoneUseType>MarketingCarrier-
Telephone-PhoneUseType</or:PhoneUseType>
<or:PhoneCountryCode>MarketingCarrier-
Telephone-PhoneCountryCode</or:PhoneCountryCode>
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 61
<or:PhoneCountryName>MarketingCarrier-
Telephone-PhoneCountryName</or:PhoneCountryName>
<or:PhoneNumber>MarketingCarrier-
Telephone-PhoneNumber</or:PhoneNumber>
</or:Telephone>
<or:Address>
<or:LocationType>MarketingCarrier-
Address-LocationType</or:LocationType>
<or:AddressLine>MarketingCarrier-
Address-AddressLine</or:AddressLine>
<or:CityName>MarketingCarrier-Address-
CityName</or:CityName>
<or:CityCodes>
<or:Code
codeContext="OTHER">MarketingCarrier-Address-CityCodes-Code</or:Code>
</or:CityCodes>
<or:LocalCityName>MarketingCarrier-
Address-LocalCityName</or:LocalCityName>
<or:StateProvince code="MarketingCarrier-
Address-StateProvince-code">MarketingCarrier-Address-StateProvince</or:StateProvince>
<or:PostCode>MarketingCarrier-Address-
PostCode</or:PostCode>
<or:Country code="MarketingCarrier-
Address-Country-code">MarketingCarrier-Address-Country</or:Country>
<or:CountryCodes>
<or:Code
codeContext="OTHER">MarketingCarrier-Address-Country-Code</or:Code>
</or:CountryCodes>
<or:Latitude>MarketingCarrier-Address-
Latitude</or:Latitude>
<or:Longitude>MarketingCarrier-Address-
Longitude</or:Longitude>
<or:Altitude>MarketingCarrier-Address-
Altitude</or:Altitude>
</or:Address>
</or:MarketingCarrier>
<or:OperatingCarrier>
<or:Name>PKP</or:Name>
<or:Code codeContext="OTHER"/>
<or:Telephone>
<or:PhoneUseType>OperatingCarrier-
Telephone-PhoneUseType</or:PhoneUseType>
<or:PhoneCountryCode>OperatingCarrier-
Telephone-PhoneCountryCode</or:PhoneCountryCode>
<or:PhoneCountryName>OperatingCarrier-
Telephone-PhoneCountryName</or:PhoneCountryName>
<or:PhoneNumber>OperatingCarrier-
Telephone-PhoneNumber</or:PhoneNumber>
</or:Telephone>
<or:Address>
<or:LocationType>OperatingCarrier-
Address-LocationType</or:LocationType>
<or:AddressLine>OperatingCarrier-
Address-AddressLine</or:AddressLine>
<or:CityName>OperatingCarrier-Address-
CityName</or:CityName>
<or:CityCodes>
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 62
<or:Code
codeContext="OTHER">OperatingCarrier-Address-CityCodes-Code</or:Code>
</or:CityCodes>
<or:LocalCityName>OperatingCarrier-
Address-LocalCityName</or:LocalCityName>
<or:StateProvince code="OperatingCarrier-
Address-StateProvince-code">OperatingCarrier-Address-StateProvince</or:StateProvince>
<or:PostCode>OperatingCarrier-Address-
PostCode</or:PostCode>
<or:Country code="OperatingCarrier-
Address-Country-code">OperatingCarrier-Address-Country</or:Country>
<or:CountryCodes>
<or:Code
codeContext="OTHER">OperatingCarrier-Address-Country-Code</or:Code>
</or:CountryCodes>
<or:Latitude>OperatingCarrier-Address-
Latitude</or:Latitude>
<or:Longitude>OperatingCarrier-Address-
Longitude</or:Longitude>
<or:Altitude>OperatingCarrier-Address-
Altitude</or:Altitude>
</or:Address>
</or:OperatingCarrier>
<or:Passengers quantity="5">
<or:Passenger passengerID="" primary="true">
<or:Type code="ADT"
codeContext="OTHER">ADT</or:Type>
<or:PersonName>
<or:Prefix>Passengers-Passenger-
PersonName-Prefix</or:Prefix>
<or:Given>Passengers-Passenger-
PersonName-Given</or:Given>
<or:Middle>Passengers-Passenger-
PersonName-Middle</or:Middle>
<or:Surname>Passengers-
Passenger-PersonName-Surname</or:Surname>
<or:Suffix>Maiden</or:Suffix>
<or:Type>Nickname</or:Type>
<or:PreferredFirstName>Passengers-Passenger-PersonName-PreferredFirstName</or:PreferredFirstName>
<or:PreferredSurname>Passengers-
Passenger-PersonName-PreferredSurname</or:PreferredSurname>
</or:PersonName>
<or:Telephone>
<or:PhoneUseType>Passengers-
Passenger-Telephone-PhoneUseType</or:PhoneUseType>
<or:PhoneCountryCode>Passengers-Passenger-Telephone-PhoneCountryCode</or:PhoneCountryCode>
<or:PhoneCountryName>Passengers-Passenger-Telephone-PhoneCountryName</or:PhoneCountryName>
<or:PhoneNumber>Passengers-
Passenger-Telephone-PhoneNumber</or:PhoneNumber>
</or:Telephone>
<or:Email>Passengers-Passenger-
Email</or:Email>
</or:Passenger>
</or:Passengers>
<or:SupplementaryServices>
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 63
<or:SupplementaryService
type="SupplementaryServices-SupplementaryService-type" code="SupplementaryServices-SupplementaryService-
code" codeContext="OTHER">
<or:Description
lang="en">SupplementaryServices-SupplementaryService-Description</or:Description>
<or:Charges>
<or:GeneralNotes>SupplementaryServices-SupplementaryService-Charges-
GeneralNotes</or:GeneralNotes>
<or:Charge
currencyCode="SupplementaryServices-SupplementaryService-Charges-Charge-currencyCode">
<or:Description>SupplementaryServices-SupplementaryService-Charges-Charge-
Description</or:Description>
<or:Notes>SupplementaryServices-SupplementaryService-Charges-Charge-Notes</or:Notes>
<or:Name>SupplementaryServices-SupplementaryService-Charges-Charge-Name</or:Name>
<or:Calculation>
<or:UnitName>SupplementaryServices-SupplementaryService-Charges-Charge-Calculation-
UnitName</or:UnitName>
<or:UnitCharge
min="10.01" max="1000.01">111.11</or:UnitCharge>
<or:Quantity
min="11.01" max="1001.01">22.22</or:Quantity>
<or:Total
min="12.02" max="1002.02">333.33</or:Total>
</or:Calculation>
<or:BillingType>SupplementaryServices-SupplementaryService-Charges-Charge-
BillingType</or:BillingType>
</or:Charge>
<or:GrandTotal
currencyCode="SupplementaryServices-SupplementaryService-Charges-GrandTotal-
currencyCode">444.44</or:GrandTotal>
<or:GeneralBillingType>SupplementaryServices-SupplementaryService-Charges-Charge-
GeneralBillingType</or:GeneralBillingType>
</or:Charges>
<or:PassengerReferences>
<or:PassengerRef id="1"/>
</or:PassengerReferences>
</or:SupplementaryService>
</or:SupplementaryServices>
<or:TrainInfo>
<or:Number>SOBIESKI 33</or:Number>
<or:Code>TrainInfo-Code</or:Code>
<or:ShortName>TrainInfo-
ShortName</or:ShortName>
<or:LongName>TrainInfo-
LongName</or:LongName>
</or:TrainInfo>
<or:Accommodation>
<or:PassengerRef>Accommodation-
PassengerRef</or:PassengerRef>
<or:Placement code="Accommodation-Placement-
code" type="TABORET">
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 64
<or:Coach>
<or:CoachNumber>CN44</or:CoachNumber>
<or:PlacementNumber
compartmentRefId="Accommodation-Placement-Coach-PlacementNumber-
compartmentRefId">PN33</or:PlacementNumber>
<or:CompartmentNumber>Accommodation-Placement-Coach-
CompartmentNumber</or:CompartmentNumber>
</or:Coach>
<or:Detail>Accommodation-Placement-
Detail</or:Detail>
</or:Placement>
<or:Meal>Accommodation-Meal</or:Meal>
</or:Accommodation>
<or:StartDetails>
<or:Address>
<or:LocationType>StartDetails-Address-
LocationType</or:LocationType>
<or:AddressLine>StartDetails-Address-
AddressLine</or:AddressLine>
<or:CityName>PARIS</or:CityName>
<or:CityCodes>
<or:Code
codeContext="OTHER">PARISGAREDEL</or:Code>
</or:CityCodes>
<or:LocalCityName>StartDetails-Address-
LocalCityName</or:LocalCityName>
<or:StateProvince code="StartDetails-
Address-StateProvince-code">StartDetails-Address-StateProvince</or:StateProvince>
<or:PostCode>StartDetails-Address-
PostCode</or:PostCode>
<or:Country code="StartDetails-Address-
Country-code">StartDetails-Address-Country</or:Country>
<or:CountryCodes>
<or:Code
codeContext="OTHER">StartDetails-Address-Country-Code</or:Code>
</or:CountryCodes>
<or:Latitude>StartDetails-Address-
Latitude</or:Latitude>
<or:Longitude>StartDetails-Address-
Longitude</or:Longitude>
<or:Altitude>StartDetails-Address-
Altitude</or:Altitude>
</or:Address>
<or:DateTime>2021-01-10T13:11:00</or:DateTime>
<or:AirportInfo>
<or:Airline code="StartDetails-AirportInfo-
Airline-code" flightNumber="1111" flightDateTime="2011-01-10T01:11:11" flightType="D"
privateAviation="true">StartDetails-AirportInfo-Airline</or:Airline>
<or:AirportName>PAR</or:AirportName>
<or:LocationCode>DN</or:LocationCode>
<or:Terminal>StartDetails-AirportInfo-
Terminal</or:Terminal>
<or:Gate>StartDetails-AirportInfo-
Gate</or:Gate>
</or:AirportInfo>
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 65
<or:Comments>StartDetails-
Comments</or:Comments>
</or:StartDetails>
<or:StopDetails>
<or:Address>
<or:LocationType>StopDetails-Address-
LocationType</or:LocationType>
<or:AddressLine>StopDetails-Address-
AddressLine</or:AddressLine>
<or:CityName>MARSEILLE</or:CityName>
<or:CityCodes>
<or:Code
codeContext="OTHER">MARSEILLESAINT</or:Code>
</or:CityCodes>
<or:LocalCityName>StopDetails-Address-
LocalCityName</or:LocalCityName>
<or:StateProvince code="StopDetails-
Address-StateProvince-code">StopDetails-Address-StateProvince</or:StateProvince>
<or:PostCode>StopDetails-Address-
PostCode</or:PostCode>
<or:Country code="StopDetails-Address-
Country-code">StopDetails-Address-Country</or:Country>
<or:CountryCodes>
<or:Code
codeContext="OTHER">StopDetails-Address-Country-Code</or:Code>
</or:CountryCodes>
<or:Latitude>StopDetails-Address-
Latitude</or:Latitude>
<or:Longitude>StopDetails-Address-
Longitude</or:Longitude>
<or:Altitude>StopDetails-Address-
Altitude</or:Altitude>
</or:Address>
<or:DateTime>2021-01-10T01:11:11</or:DateTime>
<or:AirportInfo>
<or:Airline code="StopDetails-AirportInfo-
Airline-code" flightNumber="1111" flightDateTime="2011-01-10T01:11:11" flightType="D"
privateAviation="true">StopDetails-AirportInfo-Airline</or:Airline>
<or:AirportName>LON</or:AirportName>
<or:LocationCode>DN</or:LocationCode>
<or:Terminal>StopDetails-AirportInfo-
Terminal</or:Terminal>
<or:Gate>StopDetails-AirportInfo-
Gate</or:Gate>
</or:AirportInfo>
<or:Comments>StopDetails-
Comments</or:Comments>
</or:StopDetails>
<or:EndDetails>
<or:Address>
<or:LocationType>EndDetails-Address-
LocationType</or:LocationType>
<or:AddressLine>EndDetails-Address-
AddressLine</or:AddressLine>
<or:CityName>MARSEILLE</or:CityName>
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 66
<or:CityCodes>
<or:Code
codeContext="OTHER">MARSEILLESAINT</or:Code>
</or:CityCodes>
<or:LocalCityName>EndDetails-Address-
LocalCityName</or:LocalCityName>
<or:StateProvince code="EndDetails-
Address-StateProvince-code">EndDetails-Address-StateProvince</or:StateProvince>
<or:PostCode>EndDetails-Address-
PostCode</or:PostCode>
<or:Country code="EndDetails-Address-
Country-code">EndDetails-Address-Country</or:Country>
<or:CountryCodes>
<or:Code
codeContext="OTHER">EndDetails-Address-Country-Code</or:Code>
</or:CountryCodes>
<or:Latitude>EndDetails-Address-
Latitude</or:Latitude>
<or:Longitude>EndDetails-Address-
Longitude</or:Longitude>
<or:Altitude>EndDetails-Address-
Altitude</or:Altitude>
</or:Address>
<or:DateTime>2016-01-11T02:23:00</or:DateTime>
<or:AirportInfo>
<or:Airline code="EndDetails-AirportInfo-
Airline-code" flightNumber="1111" flightDateTime="2011-01-10T01:11:11" flightType="D"
privateAviation="true">EndDetails-AirportInfo-Airline</or:Airline>
<or:AirportName>LON</or:AirportName>
<or:LocationCode>DN</or:LocationCode>
<or:Terminal>EndDetails-AirportInfo-
Terminal</or:Terminal>
<or:Gate>EndDetails-AirportInfo-
Gate</or:Gate>
</or:AirportInfo>
<or:Comments>EndDetails-
Comments</or:Comments>
</or:EndDetails>
<or:RailFares>
<or:Fare>
<or:PassengerReferences>
<or:PassengerRef id="RailFares-
Fare-PassengerReferences-PassengerRef-id"/>
</or:PassengerReferences>
<or:SegmentReferences>
<or:SegmentRef id="RailFares-
Fare-SegmentReferences-SegmentRef-id"/>
</or:SegmentReferences>
<or:ClassOfService code="RailFares-Fare-
ClassOfService-code" type="RailFares-Fare-ClassOfService-type">RailFares-Fare-
ClassOfService</or:ClassOfService>
<or:ClassCode code="RailFares-Fare-
ClassCode-code" type="RailFares-Fare-ClassCode-type">RailFares-Fare-ClassCode</or:ClassCode>
<or:FareDescription>
<or:Name>RailFares-Fare-
FareDescription-Name</or:Name>
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 67
<or:Code>RailFares-Fare-
FareDescription-Code</or:Code>
<or:Detail type="RailFares-Fare-
FareDescription-Detail-type" codeContext="RailFares-Fare-FareDescription-Detail-codeContext">RailFares-Fare-
FareDescription-Detail</or:Detail>
<or:Condition
lang="en">RailFares-Fare-FareDescription-Condition</or:Condition>
<or:Fees>
<or:Fee name="RailFares-
Fare-FareDescription-Fees-Fee-name" type="RailFares-Fare-FareDescription-Fees-Fee-type"
currencyCode="RailFares-Fare-FareDescription-Fees-Fee-currencyCode">
<or:Amount>RailFares-Fare-FareDescription-Fees-Fee-Amount</or:Amount>
<or:Description>RailFares-Fare-FareDescription-Fees-Fee-Description</or:Description>
</or:Fee>
</or:Fees>
</or:FareDescription>
<or:FarePrice currencyCode="RailFares-
Fare-FarePrice-currencyCode">444.44</or:FarePrice>
</or:Fare>
</or:RailFares>
<or:Documents>
<or:Document type="Documents-Document-
DocumentID-type" code="Documents-Document-DocumentID-code" codeContext="OTHER">
<or:DocumentID>Documents-Document-
DocumentID</or:DocumentID>
<or:AgencyAccountNumber>Documents-
Document-AgencyAccountNumber</or:AgencyAccountNumber>
<or:CreationChannel>Documents-
Document-CreationChannel</or:CreationChannel>
<or:PassengerReferences>
<or:PassengerRef id="Documents-
Document-PassengerReferences-PassengerRef-id"/>
</or:PassengerReferences>
<or:SegmentReferences>
<or:SegmentRef id="Document-
SegmentReferences-SegmentRef-id"/>
</or:SegmentReferences>
<or:IssueTimeLimit>2011-01-
10T01:11:11</or:IssueTimeLimit>
<or:IssueDateTime>2011-01-
10T01:11:11</or:IssueDateTime>
<or:DocumentStatus>HGW</or:DocumentStatus>
<or:Charges>
<or:GeneralNotes>Documents-
Document-Charges-GeneralNotes</or:GeneralNotes>
<or:Charge
currencyCode="Documents-Document-Charges-Charge-currencyCode">
<or:Description>Documents-Document-Charges-Charge-Description</or:Description>
<or:Notes>Documents-
Document-Charges-Charge-Notes</or:Notes>
<or:Name>Documents-
Document-Charges-Charge-Name</or:Name>
<or:Calculation>
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 68
<or:UnitName>Documents-Document-Charges-Charge-Calculation-UnitName</or:UnitName>
<or:UnitCharge
min="10.01" max="1000.01">111.11</or:UnitCharge>
<or:Quantity
min="11.01" max="1001.01">22.22</or:Quantity>
<or:Total
min="12.02" max="1002.02">333.33</or:Total>
</or:Calculation>
<or:BillingType>Documents-Document-Charges-Charge-BillingType</or:BillingType>
</or:Charge>
<or:GrandTotal
currencyCode="Documents-Document-Charges-GrandTotal-currencyCode">444.44</or:GrandTotal>
<or:GeneralBillingType>Documents-Document-Charges-Charge-
GeneralBillingType</or:GeneralBillingType>
</or:Charges>
<or:FormOfPayment
transactionID="Documents-Document-FormOfPayment-transactionID">
<or:Cash>Documents-Document-
FormOfPayment-Cash</or:Cash>
<or:Check>Documents-Document-
FormOfPayment-Check</or:Check>
<or:Voucher>Documents-
Document-FormOfPayment-Voucher</or:Voucher>
<or:Other>Documents-Document-
FormOfPayment-Other</or:Other>
</or:FormOfPayment>
<or:File type="Documents-Document-File-
type" coding="Documents-Document-File-coding">
<or:Representation>Documents-
Document-File-Representation</or:Representation>
<or:URL>Documents-Document-
File-URL</or:URL>
</or:File>
<or:IssueType>Documents-Document-
IssueType</or:IssueType>
<or:DocumentRules>
<or:Exchangable>Documents-
Document-DocumentRules-Exchangable</or:Exchangable>
<or:Refundable>Documents-
Document-DocumentRules-Refundable</or:Refundable>
<or:Rule type="Documents-
Document-DocumentRules-Rule-type">Documents-Document-DocumentRules-Rule</or:Rule>
</or:DocumentRules>
</or:Document>
</or:Documents>
<or:Details>
<or:Detail type="A">Details-Detail</or:Detail>
</or:Details>
</or:Rail>
</or:ProductDetails>
</Product>
</Itinerary>
<PersonName>
<Given>JOHN</Given>
<Surname>DEPP</Surname>
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 69
</PersonName>
<PhoneNumber id="1">
<PhoneText>1122334455</PhoneText>
</PhoneNumber>
<DkNumber>1234567</DkNumber>
<TicketingInfo>
<AlreadyTicketed id="1">
<Code>T-A</Code>
<Comment/>
</AlreadyTicketed>
</TicketingInfo>
<ReceivedFrom>
<Name>Kasia</Name>
</ReceivedFrom>
</NewReservation>
<ResultAction/>
</CreateReservationRQ>
RS:
<CreateReservationRS xmlns="http://webservices.sabre.com/pnrbuilder/v1_11"
xmlns:ns2="http://services.sabre.com/res/or/v1_4" xmlns:ns3="http://tds.sabre.com/itinerary">
<Success>OK</Success>
<Errors/>
<Reservation numberInParty="0" numberOfInfants="0" NumberInSegment="0">
<BookingDetails>
<UpdateTimestamp>1899-12-31T18:00:00</UpdateTimestamp>
<PNRSequence>0</PNRSequence>
<DivideSplitDetails/>
<UpdateToken>7e604ab0f9d762aa</UpdateToken>
</BookingDetails>
<POS>
<Source BookingSource="A0A0" PseudoCityCode="xxxx"/>
</POS>
<PassengerReservation>
<Passengers>
<Passenger id="4" nameType="S" passengerType="ADT" nameId="01.01" nameAssocId="1">
<LastName>DEPP</LastName>
<FirstName>JOHN</FirstName>
<Seats/>
</Passenger>
</Passengers>
<Segments>
<Segment sequence="1" id="3">
<General isPast="false">
<Line Number="1" Type="RAL" Status="GK"/>
<Vendor Code="2V"/>
<NumberInParty>5</NumberInParty>
<OriginLocation LocationCode="PARIS" Point="PAR-DN"/>
<DestinationLocation LocationCode="MARSEILLE" Point="LON-DN"/>
<DateTime>2021-01-10T13:11:00</DateTime>
<ArrivalDateTime>2016-01-11T02:23:00</ArrivalDateTime>
<ServiceInformation>HGW</ServiceInformation>
<SpaceReserved>TABORET PN33-CN44</SpaceReserved>
<ShipOrVehicleName>SOBIESKI 33</ShipOrVehicleName>
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 70
<Text>LV-1311/FR-PAR-DN/DT-11JAN/AR-0223/AT-LON-DN/NA-SOBIESKI 33/SP-
TABORET PN33-CN44/SI-HGW</Text>
</General>
</Segment>
</Segments>
<TicketingInfo>
<AlreadyTicketed id="8" index="1">
<Code>T-A</Code>
</AlreadyTicketed>
</TicketingInfo>
<ItineraryPricing/>
</PassengerReservation>
<DKNumbers>
<DKNumber>1234567</DKNumber>
</DKNumbers>
<ReceivedFrom>
<Name>KASIA</Name>
</ReceivedFrom>
<PhoneNumbers>
<PhoneNumber id="6" index="1">
<CityCode>DFW</CityCode>
<Number>1122334455</Number>
</PhoneNumber>
</PhoneNumbers>
<EmailAddresses/>
</Reservation>
</CreateReservationRS>
3 . 1 . 4 S a m p l e S T L , S t a t e f u l – T o u r p a c k a g e
RQ:
<CreateReservationRQ Version="1.11.0" xmlns="http://webservices.sabre.com/pnrbuilder/v1_11"
xmlns:or="http://services.sabre.com/res/or/v1_4">
<RequestType>Stateful</RequestType>
<ReturnOptions IncludeUpdateDetails="false" RetrievePNR="true">
<ViewName>Full</ViewName>
<ResponseFormat>STL</ResponseFormat>
</ReturnOptions>
<NewReservation>
<Itinerary>
<Product>
<or:ProductBase>
<or:ProductType>TOR</or:ProductType>
<or:VendorCode>XY</or:VendorCode>
<or:StatusCode>HK</or:StatusCode>
<or:StartPoint>KRK</or:StartPoint>
<or:StartDateTime>2015-05-30T00:00:00</or:StartDateTime>
<or:EndPoint>WAW</or:EndPoint>
<or:EndDateTime>2015-06-15T00:00:00</or:EndDateTime>
<or:Text>Text</or:Text>
<!--<or:SegmentReference>1</or:SegmentReference>-->
</or:ProductBase>
<or:ProductDetails>
<!--<or:ProductName type=""/>-->
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 71
<or:ProductName type="TOUR"/>
<or:Tour>
<or:StatusCode>GK</or:StatusCode>
<or:MessageStatus>messageStatus</or:MessageStatus>
<or:TravelType>travelType</or:TravelType>
<or:Vendor>
<or:Name>VendorName</or:Name>
<or:Code
codeContext="VendorCodeContext">VendorCode</or:Code>
<or:Telephone>
<or:PhoneUseType>VendorPhoneUseType</or:PhoneUseType>
<or:PhoneCountryCode>48</or:PhoneCountryCode>
<or:PhoneCountryName>VendorPhoneCountryName</or:PhoneCountryName>
<or:PhoneNumber>1234567890</or:PhoneNumber>
</or:Telephone>
<or:Address>
<or:LocationType>VendorAddressLocationType</or:LocationType>
<or:AddressLine>VendorAddressLine</or:AddressLine>
<or:CityName>VendorAddressCityName</or:CityName>
<or:CityCodes>
<or:Code
codeContext="VendorAddressCityContextCode">VendorAddressCityCode</or:Code>
</or:CityCodes>
<or:LocalCityName>VendorAddressLocalCityName</or:LocalCityName>
<or:StateProvince>VendorAddressStateProvince</or:StateProvince>
<or:StateProvinceCodes>
<or:Code
codeContext="VendorAddressStateProvince">VendorAddressStateProvince</or:Code>
</or:StateProvinceCodes>
<or:PostCode>VendorAddressPostCode</or:PostCode>
<or:Country>VendorAddressCountry</or:Country>
<or:CountryCodes>
<or:Code
codeContext="VendorAddressCountryContextCode">VendorAddressCountryCode</or:Code>
</or:CountryCodes>
<or:Latitude>VendorAddressLatitude</or:Latitude>
<or:Longitude>VendorAddressLongitude</or:Longitude>
<or:Altitude>VendorAddressAltitude</or:Altitude>
</or:Address>
</or:Vendor>
<or:StartDetails>
<or:Address>
<or:LocationType>StartDetailsAddressLocationType</or:LocationType>
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 72
<or:AddressLine>StartDetailsAddressAddressLine</or:AddressLine>
<or:CityName>StartDetailsAddressCityName</or:CityName>
<or:CityCodes>
<or:Code
codeContext="StartDetailsAddressCityCodeContext">StartDetailsAddressCityCode</or:Code>
</or:CityCodes>
<or:LocalCityName>StartDetailsAddressLocalCityName</or:LocalCityName>
<or:StateProvince
code="StartDetailsAddressStateProvinceCodeContext">StartDetailsAddressStateProvince</or:StateProvince>
<or:StateProvinceCodes>
<or:Code
codeContext="StartDetailsAddressStateProvinceCodeContext">StartDetailsAddressStateProvinceCode</or:Code>
</or:StateProvinceCodes>
<or:PostCode>StartDetailsAddressPostCode</or:PostCode>
<or:Country
code="StartDetailsAddressCountryCode">StartDetailsAddressCountry</or:Country>
<or:Latitude>StartDetailsAddressLatitude</or:Latitude>
<or:Longitude>StartDetailsAddressLongitude</or:Longitude>
<or:Altitude>StartDetailsAddressAltitude</or:Altitude>
</or:Address>
<or:DateTime>2015-09-30T00:00:00</or:DateTime>
<or:AirportInfo>
<or:Airline code="WS"
flightNumber="123" flightDateTime="2015-05-30T00:00:00" flightType="A"
privateAviation="true">N</or:Airline>
<or:AirportName>StartDetailsAirportInfoAirportName</or:AirportName>
<or:LocationCode>StartDetailsAirportInfoLocationCode</or:LocationCode>
<or:Terminal>StartDetailsAirportInfoTerminal</or:Terminal>
<or:Gate>StartDetailsAirportInfoGate</or:Gate>
</or:AirportInfo>
<or:Comments>StartDetailsComments</or:Comments>
</or:StartDetails>
<or:EndDetails>
<or:Address>
<or:LocationType>EndDetailsAddressLocationType</or:LocationType>
<or:AddressLine>EndDetailsAddressAddressLine</or:AddressLine>
<or:CityName>EndDetailsAddressCityName</or:CityName>
<or:CityCodes>
<or:Code
codeContext="EndDetailsAddressCityCodeContext">EndDetailsAddressCityCode</or:Code>
</or:CityCodes>
<or:LocalCityName>EndDetailsAddressLocalCityName</or:LocalCityName>
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 73
<or:StateProvince
code="EndDetailsAddressStateProvinceCode">EndDetailsAddressStateProvince</or:StateProvince>
<or:StateProvinceCodes>
<or:Code
codeContext="EndDetailsAddressStateProvinceCodeContext">EndDetailsAddressStateProvinceCode</or:Code>
</or:StateProvinceCodes>
<or:PostCode>EndDetailsAddressPostCode</or:PostCode>
<or:Country
code="EndDetailsAddressCountryCode">EndDetailsAddressCountry</or:Country>
<or:Latitude>EndDetailsAddressLatitude</or:Latitude>
<or:Longitude>EndDetailsAddressLongitude</or:Longitude>
<or:Altitude>EndDetailsAddressAltitude</or:Altitude>
</or:Address>
<or:DateTime>2015-05-30T00:00:00</or:DateTime>
<or:AirportInfo>
<or:Airline
code="EndDetailsAirportInfoAirlineCode" flightNumber="123" flightDateTime="2015-05-30T00:00:00"
flightType="A" privateAviation="true">N</or:Airline>
<or:AirportName>EndDetailsAirportInfoAirportName</or:AirportName>
<or:LocationCode>EndDetailsAirportInfoLocationCode</or:LocationCode>
<or:Terminal>EndDetailsAirportInfoTerminal</or:Terminal>
<or:Gate>EndDetailsAirportInfoGate</or:Gate>
</or:AirportInfo>
<or:Comments>EndDetailsComments</or:Comments>
</or:EndDetails>
<or:Price>
<or:Total
currencyCode="PriceTotalCurrencyCode">100</or:Total>
<or:Breakdown>
<or:References>
<or:PassengerRef id="1"/>
</or:References>
<or:Price
currencyCode="PLN">100</or:Price>
</or:Breakdown>
</or:Price>
<or:Customer>
<or:Type code="CustomerTypeCode"
codeContext="CustomerCodeContext"/>
<or:PersonName>
<or:Prefix>CustomerPersonNamePrefix</or:Prefix>
<or:Given>CustomerPersonNameGiven</or:Given>
<or:Middle>CustomerPersonNameMiddle</or:Middle>
<or:Surname>CustomerPersonNameSurname</or:Surname>
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 74
<or:Suffix>CustomerPersonNameSuffix</or:Suffix>
<or:Type>CustomerPersonNameType</or:Type>
<or:PreferredFirstName>CustomerPersonNamePreferredFirstName</or:PreferredFirstName>
<or:PreferredSurname>CustomerPersonNamePreferredSurname</or:PreferredSurname>
</or:PersonName>
<or:Telephone>
<or:PhoneUseType>CustomerTelephonePhoneUseType</or:PhoneUseType>
<or:PhoneCountryCode>48</or:PhoneCountryCode>
<or:PhoneCountryName>CustomerTelephonePhoneCountryName</or:PhoneCountryName>
<or:PhoneNumber>123456</or:PhoneNumber>
</or:Telephone>
<or:Email>CustomerEmail</or:Email>
<or:Address>
<or:LocationType>CustomerAddressLocationType</or:LocationType>
<or:AddressLine>CustomerAddressAddressLine</or:AddressLine>
<or:CityName>CustomerAddressCityName</or:CityName>
<or:CityCodes>
<or:Code
codeContext="CustomerAddressCityCodeContext">CustomerAddressCityCode</or:Code>
</or:CityCodes>
<or:LocalCityName>CustomerAddressLocalCityName</or:LocalCityName>
<or:StateProvince
code="CustomerAddressStateProvinceCode">CustomerAddressStateProvince</or:StateProvince>
<or:StateProvinceCodes>
<or:Code
codeContext="CustomerAddressStateProvinceContextCode">CustomerAddressStateProvinceCode</or:Code>
</or:StateProvinceCodes>
<or:PostCode>CustomerAddressPostCode</or:PostCode>
<or:Country
code="CustomerAddressCountryCode">CustomerAddressCountry</or:Country>
<or:CountryCodes>
<or:Code
codeContext="CustomerAddressCountryCodeContext">CustomerAddressCountryCode</or:Code>
</or:CountryCodes>
<or:Latitude>CustomerAddressLatitude</or:Latitude>
<or:Longitude>CustomerAddressLongitude</or:Longitude>
<or:Altitude>CustomerAddressAltitude</or:Altitude>
</or:Address>
<or:Age>50</or:Age>
</or:Customer>
<or:Services>
<or:Service>
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 75
<or:Description
lang="EN">ServiceDescription</or:Description>
<or:PassengerReferences>
<or:PassengerRef id="1"/>
</or:PassengerReferences>
<or:Accommodation>ServiceAccommodation</or:Accommodation>
<or:Occupancy>ServiceOccupancy</or:Occupancy>
<or:NoOfServices>1</or:NoOfServices>
<or:TravellerAllocation>ServiceTravellerAllocation</or:TravellerAllocation>
<or:ServicePrice
currencyCode="PLN">10.00</or:ServicePrice>
<or:StealBoarding>ServiceStealBoarding</or:StealBoarding>
</or:Service>
</or:Services>
</or:Tour>
</or:ProductDetails>
<or:AdditionalContent persist="true" name="Other">
<or:ParametersMap>
<or:entry>
<or:key>Vendor</or:key>
<or:value>AA</or:value>
</or:entry>
</or:ParametersMap>
</or:AdditionalContent>
<or:AdditionalContent persist="true" name="TOURSegment">
<or:ParametersMap>
<or:entry>
<or:key>Vendor</or:key>
<or:value>7T</or:value>
</or:entry>
<or:entry>
<or:key>NumberOfPeople</or:key>
<or:value>2</or:value>
</or:entry>
<or:entry>
<or:key>CityCode</or:key>
<or:value>KRK</or:value>
</or:entry>
<or:entry>
<or:key>Date</or:key>
<or:value>2021-01-20T14:12:00</or:value>
</or:entry>
<or:entry>
<or:key>TouroperatorName</or:key>
<or:value>AMERICAN EXPRESS</or:value>
</or:entry>
<or:entry>
<or:key>RoomType</or:key>
<or:value>DBLB</or:value>
</or:entry>
<or:entry>
<or:key>N</or:key>
<or:value>5</or:value>
</or:entry>
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 76
<or:entry>
<or:key>SI</or:key>
<or:value>AAAABBBBCCCC</or:value>
</or:entry>
</or:ParametersMap>
</or:AdditionalContent>
</Product>
</Itinerary>
<PersonName>
<Given>JOHN</Given>
<Surname>DEPP</Surname>
</PersonName>
<PhoneNumber id="1">
<PhoneText>1122334455</PhoneText>
</PhoneNumber>
<DkNumber>1234567</DkNumber>
<TicketingInfo>
<AlreadyTicketed id="1">
<Code>T-A</Code>
<Comment/>
</AlreadyTicketed>
</TicketingInfo>
<ReceivedFrom>
<Name>TDS_QA</Name>
</ReceivedFrom>
</NewReservation>
<ResultAction/>
</CreateReservationRQ>
RS:
<CreateReservationRS xmlns="http://webservices.sabre.com/pnrbuilder/v1_11"
xmlns:ns2="http://services.sabre.com/res/or/v1_4" xmlns:ns3="http://tds.sabre.com/itinerary">
<Success>OK</Success>
<Errors/>
<Reservation numberInParty="0" numberOfInfants="0" NumberInSegment="0">
<BookingDetails>
<UpdateTimestamp>1899-12-31T18:00:00</UpdateTimestamp>
<PNRSequence>0</PNRSequence>
<DivideSplitDetails/>
<UpdateToken>7e604ab0f9d762aa</UpdateToken>
</BookingDetails>
<POS>
<Source BookingSource="A0A0" PseudoCityCode="xxxx"/>
</POS>
<PassengerReservation>
<Passengers>
<Passenger id="4" nameType="S" passengerType="ADT" nameId="01.01" nameAssocId="1">
<LastName>DEPP</LastName>
<FirstName>JOHN</FirstName>
<Seats/>
</Passenger>
</Passengers>
<Segments>
<Segment sequence="1" id="3">
Sabre Inc. Confidential/All Rights Reserved Request and Response payload examples 77
<General isPast="false">
<Line Number="1" Type="TOR" Status="GK"/>
<Vendor Code="7T"/>
<NumberInParty>2</NumberInParty>
<Location LocationCode="KRK"/>
<DateTime>2021-01-20T00:00:00</DateTime>
<ServiceInformation>AAAABBBBCCCC</ServiceInformation>
<Tour>
<Name>AMERICAN EXPRESS</Name>
<NumberOfNights>5</NumberOfNights>
<RoomType>DBLB</RoomType>
</Tour>
<Text>AMERICAN EXPRESS/DBLB/N-5/SI-AAAABBBBCCCC</Text>
</General>
</Segment>
</Segments>
<TicketingInfo>
<AlreadyTicketed id="8" index="1">
<Code>T-A</Code>
</AlreadyTicketed>
</TicketingInfo>
<ItineraryPricing/>
</PassengerReservation>
<DKNumbers>
<DKNumber>1234567</DKNumber>
</DKNumbers>
<ReceivedFrom>
<Name>TDS_QA</Name>
</ReceivedFrom>
<PhoneNumbers>
<PhoneNumber id="6" index="1">
<CityCode>DFW</CityCode>
<Number>1122334455</Number>
</PhoneNumber>
</PhoneNumbers>
<EmailAddresses/>
</Reservation>
</CreateReservationRS>
Sabre Inc. Confidential/All Rights Reserved Defined Errors 78
Defined Errors
4 . 1 E r r o r L i s t
There is a list of most common error messages that are returned presented below.
Error Code Message
500600 Unknown Update Reservation error
500601 UNABLE TO PROCESS
500602 INPUT DATE ERROR CONDTION
500603 INPUT CITY ERROR CONDTION
500604 INPUT TIME ERROR CONDTION
500605 INPUT QUEUE ERROR CONDTION
500606 INPUT PIC ERROR CONDTION
500607 CITY NOT AUTHORIZED
500608 FQP ACTION MISSING
500609 Item not found
500610 Name mismatch
500611 Segment mismatch
500612 Name not found
500613 Name unrecoverable error
500614 Name Ids mismatch
500615 Max # of individual names
500616 DATA FORMAT ERROR
500617 Invalid Lrec Key
500618 Invalid Lrec Type
500619 Lrec not found
500620 Max # of air segments
500621 Value can never be zero
500622 Invalid Requested Action
500623 Duplicate Lrec found
500624 Item decency error
500625 Item size error
500627 Format Not supported
500628 Invalid Lrec Field Setting
500629 MAX TAX COUNT REACHED
500630 MAX TKT COUNT REACHED
500632 INVALID AE SELL ENTRY
500633 CHECK NUMBER OF SERVICES
500634 NO PRICING DATA PERFORM WPAE ENTRY
500635 CHECK SERVICE NUMBER
500648 INVALID AE UPDATE ENTRY
4
Sabre Inc. Confidential/All Rights Reserved Defined Errors 79
500649 CHECK ITEM NUMBER
500650 PARAMETER NOT VALID
500651 CHECK PNR
500652 Invalid Tax Sequence Number
500653 Update on Tax not allowed, check tax item
500654 TAX Data not present
500655 Update on seg not allowed, check segment count
500656 Update on seg not allowed, use cancel then create entry
500664 INVALID AE CREATE ENTRY
500665 MANDATORY FIELDS ARE NOT ALL PRESENT
500666 INVALID DATE
500667 NEED SEG IN PNR
500668 NEED NAME IN PNR
500669 DUPLICATE AE DATA
500680 ANCS Messaging Error
500681 Ancillary re-price was not successful,
500682 Ancillary price from pricing is different than ancillary price from Air Extras
field in PNR
500683 Ancillary price from pricing is not available
500684 ANCS Unknown error
500685 ANCS AthXml or AthId is required
500686 ANCS Security data are required
500687 Check Currency
500688 Seat Sell is not allowed
500689 Please include UpdateID for each ancillary in your UpdateReservation
request to get more detailed information about errors that may be returned in
the response.
500697 Update Reservation processing error
500698 PSS MOM messaging timeout
500699 PSS MOM messaging error
500701 [VALIDATION ERROR] Id could not be null or empty
500800 ET processing error PNR PREVIOULSY UPDATED ? LATEST
CHANGES NOT APPLIED
Sabre Inc. Confidential/All Rights Reserved Defined Errors 80
4 . 2 S a m p l e E r r o r R S
Invalid “RequestType” in RQ message
RS:
<CreateReservationRS xmlns="http://webservices.sabre.com/pnrbuilder/v1_11"
xmlns:ns2="http://services.sabre.com/res/or/v1_4"
xmlns:ns3="http://tds.sabre.com/itinerary">
<Errors>
<Error>
<Code>2</Code>
<Message>Marshalling exception (null; cvc-enumeration-valid: Value
'Change' is not facet-valid with respect to enumeration '[Stateful, Stateless,
Payload]'. It must be a value from the enumeration.; )</Message>
<Severity>MODERATE</Severity>
</Error>
</Errors>
</CreateReservationRS>
Invalid “ProductName” in RQ message
RS:
<CreateReservationRS xmlns="http://webservices.sabre.com/pnrbuilder/v1_11"
xmlns:ns2="http://services.sabre.com/res/or/v1_4"
xmlns:ns3="http://tds.sabre.com/itinerary">
<Errors>
<Error>
<Code>700432</Code>
<Message>Reservation Orchestration Error Caused by: [Invalid
ResOrchAction [Invalid product type: COUC]]</Message>
<Severity>MODERATE</Severity>
</Error>
</Errors>
</CreateReservationRS>
Sabre Inc. Confidential/All Rights Reserved Frequently Asked Questions 81
Frequently Asked Questions
5 . 1 W h o s h o u l d I c o n t a c t f o r q u e r y h e l p
Should you require any additional information about this service please send email to
[email protected] for help. When sending requests to Sabre Web Services Support Desk,
please consider the specific information contained in our support site http://myhelp.sabre.com/wbsvc/ . In
case of pressing issues you can reach the Sabre Webservices team by phone at (800) 678-9460 (USA),
(682) 605-5570 (Canada), +598 (2) 518-6020 (International).
5 . 2 F i r s t L e v e l S u p p o r t
First Level Support will be provided by the Sabre Webservices Team who will contact Application
Development on Call if required.
5