Getting Started

Introduction

This guide is for architects and developers to learn how to compose XML formatted requests for the GetReservationRQ API. This release covers XML requests and responses which allow client applications to retrieve PNR data including Itinerary, Passenger information, and more. The GetReservationRS message can be returned in STL and its respective details can be found in the WSDL file.

Overview

The purpose of this document is to describe how the web service works and provide details how to create a successful request transaction. This document also provides details on the response transaction, including any errors. The content of each chapter is as follows:

• Chapter 1, Getting Started explains the purpose of the document, details any critical information, and provides a functional overview.
• Chapter 2, GetReservationRead Request and Response structure contains descriptions of the attributes and elements in the response schema.
• Chapter 3, Documentation Updates contains the necessary filenames to run GetReservationRQ.
• Chapter 4, Error Codes contains error codes and descriptions.
• Chapter 5, Technical Support contains information on where to get help.
• The Glossary provides a list of terms used in this document.

Availability

This service can be used by:

• Sabre Dev Studio subscribers.
• Sabre Travel Network customers – travel agencies working on Sabre® Red Workspace™ and other Sabre user interfaces.
• Airlines
• Third-party customers.

Both internal and external consumers can gain benefits from GetReservationRQ as part of Sabre API. The service runs in 24x7 mode. In case of any planned maintenance windows, we send standard notifications in advance. We offer the standard service functionalities to all the clients, but availability varies depending on the type of request used:

• Stateless requests can be used by airlines only.
• Stateful requests can be used by both airlines and travel agencies. (Default type of request).

Specific service capabilities may require dedicated activations. In case of any doubts, we recommend contacting our Technical Support. Please contact us also if you plan to start using the service intensively with a high volume of requests, so that we will be able to tune the service to be fit for your purposes and ensure the search process will always run smoothly.

High-Level Design

Key changes compared to previous version

GetReservationRQ 1.19 User Guide introduced a couple of changes:

• New fields for storing additional information regarding PNR (for authorized users only)

  Enables authorized users to mark PNRs as suspicious using UpdateReservationRQ API and read that information using GetReservationRQ.

• Informational segment flag inclusion

  Introduces a new indicator to identify OA flights that are booked by a 3rd party.

• New capabilities for hotel content (CRUD) The new Lodging Platform will enable customers to connect to different sources of content. They will be able to provide rates from different suppliers for the same hotel and allow the customer to choose which one to book.

  Ability to create hotel bookings in a stateless way regardless of content source:

• Traditional hoteliers through the GDS path (Hilton, Marriott etc).

• Suppliers through a direct connect, mostly hotel aggregators (EAN, GTA, HotelBeds etc).

• Agency sourced content, loaded into our extranet – agency private rates.

This functionality will be available in Q42018. A description will be provided after activation in production.

• Views and subject areas

  • Default and Full views will now support adding SubjectAreas into the request.
  • New subject areas ACTIVE and HISTORICAL have been added to enable custom views creation.

• Ability to choose PQ (PriceQuoteServicesRQ) service version

  Supports the ability to specify the PriceQuoteServicesRQ service version instead of defaulting to the latest version in PROD

• Ability to retrieve PayInfo from PNR

  PayInfo contains data in the PAY field in the PNR