APIs

Get travel information on demand with our REST and SOAP APIs.

What's in it for you?

  • Incorporate rich shopping content from the Sabre® travel marketplace
  • Access market insights, such as busiest travel times and flight price ranges others recently booked
  • Create an enriched shopping experience through map-based, large calendar and budget shopping applications
  • Receive sub-second inspirational shopping results
  • Build a fully-customized application, whether you are a full-service travel company or only focused on searching for travel

With our portfolio of over 100 SOAP APIs and a growing collection of REST APIs, you can incorporate services across the entire travel journey — from dreaming, to planning, to purchasing and servicing trips.

Try our REST APIs to enable new air shopping experiences, including sub-second inspirational and theme shopping, as well as intelligence services to help users make more informed choices. Our SOAP APIs allow you to customize your applications with an end-to-end workflow tailored to your exact needs.

  • Search for air, car, hotel, rail, and cruise
  • Service travel reservations
  • Build process automation tools
  • Manage customer profiles
Name Category Function API Type Link

  Alert! There are no items that match your filter.

The Create Passenger Name Record API is an orchestrated API that bundles several functions and operations into a single API call. This API specifically provides the capability to create a Passenger Name Record (PNR) including air segments in a single call. Go to documentation

The Seat Map API returns real-time seat map and specific seat pricing and availability information for a given aircraft. Go to documentation

The Advanced Calendar Search API retrieves up to 200 roundtrip flight itineraries with published fares available from the Sabre cache for a specific origin, destination, and length of stay across a large set or range of travel dates. The API returns and sorts these itineraries by fare in ascending order, from lowest to highest. Go to documentation

The Bargain Finder Max Alternate Airport Shop API allows you to define up to 20 airports per origin and/or destination. The response will be the lead fares with the corresponding flight itinerary and fare breakdown. Go to documentation

Bargain Finder Max Alternate Date service is used to search for the lowest available priced itineraries based upon +/-1 or +/-3 alternate dates. A wide range of user-specified criteria can be applied to the search. Go to documentation

Bargain Finder Max (BFM), our best-in-class low fare search product, is used to search for the lowest available priced itineraries based upon a travel date. A wide range of user-specified criteria can be applied to the search. Go to documentation

The Destination Finder API retrieves a then current nonstop lead fare and an overall lead fare available to destinations from a specific origin on round-trip travel dates from the Sabre® cache. (A lead fare is the then current lowest published fare available via the Sabre cache for an origin, destination, and round-trip date combination.) Go to documentation

The Flights To API returns 20 of the lowest published fares available for a given destination. Go to documentation

The InstaFlights Search API retrieves round-trip flight itineraries with published fares and fare breakdowns available from the Sabre® cache for a certain origin, destination, and round-trip travel dates. The origins and destinations are airport codes. Go to documentation

The Lead Price Calendar API retrieves a then current nonstop lead fare and overall lead fare available on future calendar dates for a specific origin, destination, and lengths of stay from the Sabre® cache. (A lead fare is the then current lowest published fare available from the Sabre cache for an origin, destination, and round-trip date combination.) Go to documentation

The Fare Range API returns the median, highest, and lowest published fares that were ticketed via the Sabre® GDS during the previous 4 weeks for each of the future departure dates in a range, using the specific origin, destination, and length of stay in the request. Go to documentation

The Low Fare Forecast API forecasts the price range into which the lowest published fare that is available via the Sabre® GDS is predicted to fall within the next 7 days, for a specific origin and destination on specific round-trip travel dates. (The predicted high and low price range is called the fare range.) Go to documentation

The Low Fare History API returns each day of the past two weeks' lowest published fares for a given city/date pair. Go to documentation

The Top Destinations API retrieves top booked leisure destinations from a given origin and returns them in ascending rank order. The API looks up the traffic volume booked via the Sabre® GDS to the top destinations for the previous 2 weeks. It returns up to 50 results per origin by rank — rank one is most popular; whereas, rank 50 is least popular. Go to documentation

The Travel Seasonality API rates weekly traffic volumes to certain destination airports. The API looks up the traffic volume booked via the Sabre® GDS to the requested destination airport for each of the previous 52 weeks. It compares the booked traffic for each week to each of the other previous 51 weeks, and rates each week. Go to documentation

The Airports at Cities Lookup supplemental API retrieves our list of major airport codes that are associated with a single multi-airport city code (also called a MAC code) in the request. A multi-airport city, or MAC, is a city that is served by multiple major airports. For example, when your request provides the CHI MAC code, the API retrieves a list of airport codes that we associate with Chicago. Go to documentation

The City Pairs Lookup supplemental API retrieves city pairs that we support as a combination of origin and destination airport codes. You can pass any of these origin and destination airport city pairs in our air shopping and intelligence REST APIs, provided that the APIs support the locations. For example, this API retrieves the SJU-MIA city pair (San Juan International Airport in Puerto Rico to Miami International Airport in the U.S.). Because most of our REST APIs support origins in the U.S., Puerto Rico, and the U.S. Virgin Islands, you can pass this city pair in most of our API requests. Go to documentation

The Countries Lookup API retrieves a list of origin and destination countries. These countries can be used as a filter in applicable REST APIs. This API is point of sale specific (each point of sale supports a unique list of origin and destination countries). Go to documentation

The Custom Theme enables you to modify and customize themes. You can create a custom travel theme and associate that theme with airport and multi-airport city (MAC) codes. You can then pass your custom theme as a filter in a request with any REST API that supports a theme. The response will be destinations that are associated with your theme. Go to documentation

The Destinations by Carrier API returns a list of destinations and the corresponding (direct) flights from a given origin. Go to documentation

The Multi-Airport City Lookup supplemental API retrieves a list of multi-airport city codes, called MAC codes. A multi-airport city, or MAC, is a city that is served by multiple major airports. You can use these MAC codes in an Airports at Cities Lookup API request to retrieve airports that are associated with the MAC code. Go to documentation

Point of Sale Country Code Lookup is a supplemental API that retrieves a list of supported point of sale country codes and associated country names. Go to documentation

The Theme Airport Lookup retrieves a list of destination airport codes that are associated with the theme in the request. A theme is similar to a travel category, and is based on geography, points of interest, or recreational activities, such as beaches, national parks, or skiing. Go to Documentation

The Travel Seasonality Airports Lookup supplemental API retrieves airports that we support as a destination airport. You can pass any of these destination airports in a Travel Seasonality API request. Go to documentation

The Travel Theme Lookup retrieves a list of themes. A theme is similar to a travel category, and is based on geography, points of interest, and recreational activities, such as beaches, national parks, or skiing. If you want to use the Destination Finder to shop for lead fares to destinations that are based on a theme, you must include one of the themes that Travel Theme Lookup returns. (Travel Theme Lookup is a supplemental API.) Go to documentation

The Car Availability API returns real-time rental car pricing and availability information. The API retrieves rental car availability and total pricing data based on a specified pickup location and travel date. Go to documentation

The Get Vehicle Media API returns the available image content and associated vehicle data for given vehicles available for rental. Go to documentation

The Get Hotel Content API returns image and descriptive content for up to 50 Sabre Hotel IDs in a single request. Go to documentation

The Get Hotel Descriptive Info API returns requested descriptive content for a series of Sabre hotel IDs. Go to documentation

The Get Hotel Image API returns the default image for a given Sabre hotel(s). Go to documentation

The Get Hotel List API returns hotels and their details according to the search criteria provided in the request. Go to documentation

The Get Hotel Media API returns the available image content for a given Sabre Hotel(s). Go to documentation

The Get Hotel Chain Info API allows the client to submit a request for a hotel marketer name and chain code. Go to documentation

The Get Hotel Content Change API allows a client to submit a content update request with check-in and check-out dates and obtain a list of hotels that have updated their descriptive content. Go to documentation

The Airline Alliance Lookup API returns the airline alliance member information associated with a specified airline alliance group code. Go to documentation

The Aircraft Equipment Lookup API returns the aircraft name associated with a specified IATA aircraft equipment code. Go to documentation

The Airline Lookup API returns the airline name associated with a specified IATA airline code. Go to documentation

The Custom Region API is a suite of APIs that provides customers with the ability to create and customize regions. Go to documentation

The Custom Response View API allows you to customize the response of a given REST API. Go to documentation

The Geo Autocomplete API returns a list of location predictions for text-based geographic search queries. Go to documentation

The Geo Code API returns the geographic information of a given location. Go to documentation

The Geo Search API identifies airports or Sabre hotel(s) that fall within a given geographic search location using a radius search. Go to documentation

The Response View API allows you to use a preformatted Sabre response view for a given REST API. Go to documentation

Air Extras (AncillaryPriceRQ) is used to return a list of Air Extra products and their prices available for a given itinerary. Air Extras handles both pre-ticketed and post-ticketed ancillary pricing. These Air Extras are considered supplementary services that the carrier offers the customer. Go to documentation

Air Fare Rules (OTA_AirRulesLLSRQ) is used to display air fare rules, based upon city pair, date, fare basis code and carrier code. Examples of what you can specify include to return fare routing-related information, a global indicator, a ticket designator, an account code, a corporate ID, a private or public fare indicator, display historical fare rules based upon a fare basis code, date, class of service, as well as a carrier code. Go to documentation

Air Fare Rules from Price (PO_RulesFromPriceRQ) supports the fare and rule display of fares from the response of No PNR Pricing. It can display rules for up to 16 fares from fare option response of No PNR pricing within a single request. It can also display rule menu, header and routing information by request. Go to documentation

Air Fares by City Pairs (FareLLSRQ) is used to search for fares associated with particular markets. Using this API, you can perform a basic fare quote, specify preferred airlines, specify a currency code, specify to return base fare and tax information, specify an account code, specify a corporate ID, specify a fare basis code, specify a fare level, specify a global indicator, specify a fare basis code/ticket designator, and several other parameters. Go to documentation

Book Air Segment (OTA_AirBookLLSRQ) is used to book one or more flight segments. Using this API, you canbook a one way or round trip itinerary, or book an open itinerary. Other parameters include equipment and flight information, number in party, origin and destination information, booking code. Go to documentation

Book from Air Availability (ShortSellLLSRQ) is used to short sell direct access airline flight segments from an air availability response. You can also specify a married connection from a successful, direct access-based Air Availability response, or request with multiple connections/booking classes. Go to documentation

Calculate Air Tax for Itinerary (OTA_AirTaxRQ) is used to calculate applicable taxes for one or more air travel itineraries, and for one or more passenger types on each itinerary. This service can calculate taxes for up to 50 itineraries. Each itinerary can contain multiple flight segments and multiple fare break points. Go to documentation

Cancel Air Seat (AirSeatCancelLLSRQ) is used to cancel a previously reserved seat for a selected itinerary segment. Go to documentation

Cancel Itinerary Segments (OTA_CancelLLSRQ) is used to cancel itinerary segments contained within a passenger name record (PNR). Go to documentation

Delete Price Quote (DeletePriceQuoteLLSRQ) is used to delete price quote records. Please note that a PNR must be present in the current work area/session prior to calling this API. Go to documentation

Display Price Quote (DisplayPriceQuoteLLSRQ) is used to display stored fare information contained within a passenger name record (PNR). Go to documentation

Fare Rules from Air Price (RulesFromPriceLLSRQ) is used to retrieve fare rule information from a pricing response. OTA_AirPriceLLSRQ must be executed prior to calling RulesFromPriceLLSRQ. Go to documentation

Flight Details (VerifyFlightDetailsLLSRQ) is used to verify details about a specific flight number on a specific date. Using this API, you can verify flight details for a range of lines in a Get Air Availability response or verify flight details for multiple, nonconsecutive lines in a Get Air Availability response. Go to documentation

Orchestrated Air Booking (EnhancedAirBookRQ) is used to book, price, and compare prices for a maximum of 99 flight segments. Before using this service, it is assumed that the client has completed shopping and has chosen flights to sell. Go to documentation

Price Air Itinerary (OTA_AirPriceLLSRQ) is used to price air itineraries. There must be at least one flight segment in the current work area/session with two seats sold. Go to documentation

Price with Itinerary (PO_PNRPricingRQ) is used to support PNR Pricing (also referred as Itinerary Pricing) functionality. Many parameters are provided in this API including, currency code, base fare amount, price, fare basis code, passenger type, airline code, security fee, nation and station code, arrival and departure code, and ancillary fee group code. Go to documentation

Price without Itinerary (PO_NoPNRPricingRQ) is used to support No PNR Pricing functionality. This API prices up to 16 segments and up to a maximum of four passenger types without a PNR. It provides up to 24 fare options per passenger type. Go to documentation

Reserve Air Seat (AirSeatLLSRQ) is used to reserve a seat for an itinerary segment or segments. Go to documentation

Seat Map (EnhancedSeatMapRQ) used to display seat map with prices, for a given carrier code, flight number, class of service, board point, off point and departure date. Information returned response contains the seat map data and the exact prices for each paid seat, in addition to a seat map banner. Go to documentation

Sell Miscellaneous Segment (MiscSegmentSellLLSRQ) is used to sell OTH, MCO, PTA, or INS miscellaneous segment types. Go to documentation

Auto Price Air Exchanges (AutomatedExchangesLLSRQ) is used to price an air ticket exchange. This service is marketed to customers as Automated Exchanges (formerly QREX Plus). AutomatedExchangesLLSRQ is the replacement for the QREXLLSRQ service. Go to documentation

Create PhaseIV Ticket Record (PhaseIVAddInfoLLSRQ) is used to create a Phase IV ticket record, which is used for manual pricing. Go to documentation

Get Credit Card Approval (CreditVerificationLLSRQ) is used to obtain credit card approval through the Sabre system. Go to documentation

Get EM Documents (EMD_DisplayLLSRQ) is used to display electronic miscellaneous documents. Go to documentation

Get EMD Transactions (DailyEMD_ReportLLSRQ) is used to display an audit trail for a particular agency, listing relevant EMD transactions for a particular date or range of dates. Go to documentation

Get eTicket Details (eTicketCouponLLSRQ) is used to display eTicket coupon data for a specified ticket number. eTicket coupon-related data is pulled from Sabre's own internal ticketing database so there is a slight chance that the coupon status could be different from the coupon status in the carrier's own eTicket database. Go to documentation

Get Refund Report (DailyRefundReportLLSRQ) is used to display an refund audit trail for a particular agency, listing relevant refund transactions for a particular date or range of dates. Go to documentation

Get Sales Report (DailySalesReportLLSRQ) is used to display an audit trail for a particular agency, listing relevant transactions for a particular date or range of dates. Go to documentation

Get Unused eTickets (UnusedeTicketReportLLSRQ) is used to display a report of unused eTickets. Go to documentation

Issue Air Ticket (AirTicketLLSRQ) is used to issue air tickets. These can be paper, electronic, or paper tickets for airline use only. Go to documentation

Revalidate eTicket (eTicketRevalidateLLSRQ) is used to allow a client application to revalidate an electronic ticket for a participating carrier. Go to documentation

Void Air Ticket (VoidTicketLLSRQ) is used to void air tickets. Please note that a PNR must be present in the current API work area/session prior to calling this service. Go to documentation

Air Availability (OTA_AirAvailLLSRQ) is used to ask for flights and the corresponding class availability information for a given origin, destination and travel date. Go to documentation

Air Schedules And Availability (AirSchedulesAndAvailabilityRQ) is used to retrieve schedules and availability for one or more given origins, destinations and travel dates. Go to documentation

Alternate Airport Shop (BargainFinderMax_ASRQ) allows the user to define up to 20 airports at origin and/or at destination to be shopped. Service will return at least one lowest fare per airport pair plus more options in low to high order. Go to documentation

Bargain Finder Max (BargainFinderMaxRQ), our best-in-class low fare search product, is used to search for the lowest available priced itineraries based upon a specific date. A wide range of user-specified criteria can be applied to the search. For the complete list, please consult the request and response design documentation. Go to documentation

Basic Fare Shop (BargainFinderPlusLLSRQ) is used to search for lower fares on an existing itinerary as well as other flights that serve the same routing. Go to documentation

BFM Alternate Date (BargainFinderMax_ADRQ) service is used to search for the lowest available priced itineraries based upon +/-1 or +/-3 alternate dates. A wide range of user-specified criteria can be applied to the search. Go to documentation

BFM Shop Across Passenger Type (BargainFinderMax_SAPTRQ) is used to search for the lowest available priced itineraries and compare the prices for multiple passenger types based upon a specific date. A wide range of user-specified criteria can be applied to the search. Go to documentation

Calculate Air Mileage (MileageLLSRQ) is used to compute air routing mileage. The mileage is based on the air routing from origin to destination as obtained from IATA. If a connecting flight is involved the mileage to and from the connecting city is included. Go to documentation

Flight Schedules (OTA_AirScheduleLLSRQ) is used to ask for scheduled flights regardless of availability for a given origin, destination and travel date. Go to documentation

Get Air Connection Points (AirConnectionPointLLSRQ) is used to retrieve general information about departure and arrival connection locations of airline flights. Go to documentation

Get Air Connection Times (AirConnectionTimeLLSRQ) is used to retrieve information regarding connection times between two carriers, with the option of excluding one or more carriers. Go to documentation

Get Flight Details (OTA_AirFlifoLLSRQ) is used to retrieve flight information (FLIFO) details for a specific flight. Go to documentation

Shop by Specific Fare (PromotionalShoppingRQ) returns a list of dates when the chosen fare is applicable, designating also whether or not the fare is available. The user then sends a specific date and the service returns a list of applicable and available flight schedules for that date. Go to documentation

Shop Exchange Options (ExchangeShoppingLLSRQ) is used to find the best reissue price after changing an itinerary on a previously ticketed PNR. The API searches for up to 19 low-price reissue options on other flights for the same day. Go to documentation

Encode Decode IATA Codes (EncodeDecodeLLSRQ) is used to encode city, airport, country, or state names into their corresponding IATA Codes, or to decode the IATA Codes for a city, country, or state into its corresponding name. Go to documentation

Get Vendor Codes (VendorCodesLLSRQ) is used to display the different DU tables that are available in the Sabre system, which offer extensive lists of various types of information such as charge descriptor codes, credit card codes, or different types of associates that participate in the Sabre system. Go to documentation

Book Car Reservation (OTA_VehResLLSRQ) is used to reserve one or more rental cars. A PNR containing at least one passenger name must be in the work area/session is a pre-condition to using this API. Go to documentation

Cancel Request Message (RailCancelRQ) performs a booking cancellation. The request passes the Sabre PNR Locator. Logic cancels the related SNCF reservation, and then it cancels the Sabre PNR. The Cancel web service does not require the PNR to be loaded into the current session – it has ability to load the requested PNR into the session by itself. Go to documentation

The Car Rate Code Rules (VehRateRulesLLSRQ) is used to display the rules for a vehicle rental rate code. When requesting rate rules you include a reference to the specific line number in the Car Availability Rate API response, which you loaded into the Sabre work area (AAA). Go to documentation

Car Rates Non-Airport (VehQuoteLocationListLLSRQ) is used to request a non-airport car quote. Go to documentation

The RailManageBookingRQ service is used to carry out reservation (booking) for one or more journeys between specified locations, on specific dates, for a specific quantity and type of passengers, to carry out booking modification on a PNR that has not been issued or to estimate the booking price and issuing tickets. Go to documentation

Modify Car Reservation (VehResModifyLLSRQ) is used to modify a confirmed vehicle segment in a passenger name record (PNR). Go to documentation

Manage Rail Post Booking (RailManageAfterSalesRQ) is used to carry out after sales operation on a PNR that has been completely or partially issued. Go to documentation

Manage Rail Ticketing (RailManageTicketRQ) is used to issue a ticket, cancel a ticket already issued, and send a confirmation email to the passengers of a PNR with dematerialized tickets. Go to documentation

Car Availability (OTA_VehAvailRateLLSRQ) includes a response for car availability and rates. It includes Car rates and Total Pricing at a single location. You can add in the request to shop for special equipment and services including pricing and availability. (up to 10). Go to documentation

Car Location Details (OTA_VehLocDetailLLSRQ) is used to request detailed information about a specific car rental location, based on a city code, vendor code, or both, specify pickup/drop off times. It also returns detailed information about the location such as hours and contact information. Go to documentation

Car Locations (VehLocationFinderLLSRQ) is used to search for vehicle rental locations based on city names, addresses, zip codes, points of interest passed as brief text descriptions (for example, “Sears tower”), hotel location codes, or a hotel segment in a booked Passenger Name Record (PNR). Go to documentation

Car Locations by Airport (VehLocationListLLSRQ) This API is used to display locations of car rental vendors for a specific airport or city code for vendor coded to the specific input airport code. Go to documentation

Shop Rail (RailShopRQ) is used to return availability options and estimated prices for groups or subscription cards. Go to documentation

Encode Decode Rail Station (RailLocationRQ) encodes and decodes rail stations by name or by code. When a rail station is decoded by name, all fully or partially matching options can be returned. If no station exists within the provided location, other stations located nearby can be provided. Go to documentation

For Deutsche Bahn itineraries, please use Get DB Rail Reservation (RailResRetrieveRQ). This service provides XML with back office data available per Deutsche Bahn (NVS) order on the web service request. Go to documentation

Get Rail BSG Itineraries (RailItemSearchRQ) is used to retrieve list of BSG PNRs and retrieve list of passenger subscription cards. Upon success, the output shows a list of BSG PNR?s which are in the queue for PCC and a list of one or more card(s) which are related to the passenger whose information was specified in the input. Go to documentation

Retrieve Rail Itinerary (RailReservationReadRQ) is used to retrieve vendor rail reservation. Upon success, the output shows the PNR content (PNR reference, travelers, itinerary, fares,tickets, delivery modes, contacts etc.). Go to documentation

Synch Rail Itineraries (RailPNRSynchRQ) allows synchronization and import of vendor PNRs into Sabre PNR. It can be also used to import vendor (currently ACP or SNCF) PNR into a new Sabre PNR. Go to documentation

Modify Hotel Reservation (HotelResModifyLLSRQ) is used to modify a confirmed hotel segment in a passenger name record (PNR). Go to documentation

Book Hotel Reservation (OTA_HotelResLLSRQ) is used to reserve one or more hotel rooms and create a hotel segment in a passenger name record, (PNR). This API allows client applications to either blind sell a hotel reservation or to sell a hotel reservation from a hotel description. Go to documentation

Modify Hotel Reservation (HotelResModifyLLSRQ) is used to modify a confirmed hotel segment in a passenger name record (PNR). Go to documentation

Hotel Availability (OTA_HotelAvailLLSRQ) is typically the first step in the shopping process and provides you with rate ranges and real time availability across a broad set of properties using a basic airport code, city code, or city name search, with the optional addition of other search criteria. Requests can be made using specific negotiated rate codes, up to 331 days in advance, and for up to 9 guests and up to a 220 day maximum length of stay. Go to documentation

Hotel Property Description (HotelPropertyDescriptionLLSRQ) provides detail on available room rates by room and rate type for a single property. Responses are based on real time requests to hotel suppliers with actual rates and rooms available at the time of request. The API allows the user to provide rate codes and qualifiers to shop for the applicable rates, and robust property descriptive content is provided with each rate. Go to documentation

Hotel Rate Description (HotelRateDescriptionLLSRQ) provides all applicable rules, policies, and restrictions governing use of a specific hotel rate. The API response also may include a breakdown of all charges including base rate, changes over the stay, all taxes in detail, and an overall estimated cost. Go to documentation

Copy Profile to Itinerary (EPS_EXT_ProfileToPNRRQ) is a Sabre Profiles web service that allows the user to move profile data into the Sabre Passenger Name Record (PNR). Go to documentation

Cancel Profile Search (EPS_EXT_OfflineJobCancelRQ) is used for canceling an offline job that has not yet been processed and waits in the queue (with status NEW). Go to documentation

Create Profile Search (EPS_EXT_OfflineJobCreateRQ) is used for creating new jobs and specifying the search criteria. Go to documentation

Delete Profile Search (EPS_EXT_OfflineJobDeleteRQ) is used for deleting the job that has already been processed (status other than NEW). Go to documentation

Get Profile Search Results (EPS_EXT_OfflineJobReadResultRQ) is used for displaying job results which consist of the list of profile summaries for the profiles matching the search criteria. Go to documentation

List Profile Searches (EPS_EXT_OfflineJobRetrieveRQ) is used for listing all the jobs in a given domain along with their statuses. Go to documentation

Create Custom Field Codes (EPS_EXT_ProfileDataSrvRQ) is a Sabre Profiles Web service to perform operations on meta data like creating custom defined categories, etc. Go to documentation

Create Profile Objects (EPS_EXT_ProfileCreateRQ) is a Sabre Profiles web service that creates Profiles, Templates, Filters, Formats, Metadata, Validators, and Associations. Go to documentation

Delete Profile Objects (EPS_EXT_ProfileDeleteRQ) is a Sabre Profiles web service that creates Profiles, Templates, Filters, Formats, Metadata, Validators and Associations. Go to documentation

Get Multiple Profile Objects (EPS_EXT_ProfileBulkReadRQ) is a Sabre Profiles web service that mimics existing ReadRQ and reads multiple profiles, filters, and formats in a single call. Go to documentation

Read Profile History (EPS_EXT_ProfileHistoryRQ) is a Sabre Profiles web service that allows a customer to track the types of actions that have been performed on the subject areas for Traveler, Operational, Corporation, Travel Agency, and Travel Agent Profiles. Go to documentation

Update Profile Objects (EPS_EXT_ProfileUpdateRQ) is a Sabre Profiles web service that creates Profiles, Templates, Filters, Formats, Metadata, Validators and Associations. Go to documentation

Search Profile Objects (EPS_EXT_ProfileSearchRQ) is a Sabre Profiles web service that creates Profiles, Templates, Filters, and Formats, Metadata, Validators, and Associations. Go to documentation

Update Profile Objects (EPS_EXT_ProfileUpdateRQ) is a Sabre Profiles web service that creates Profiles, Templates, Filters, Formats, Metadata, Validators and Associations. Go to documentation

Create Role (Roles_EXT_CreateRQ) is a Sabre Profiles User Roles web service to create role with permission codes. Go to documentation

Delete Role (Roles_EXT_DeleteRQ) is a Sabre Profiles User Roles web service to delete roles with permission codes. Go to documentation

Read Role (Roles_EXT_ReadRQ) is a Sabre Profiles User Roles Web service to read roles with permission codes. Go to documentation

Search Role (Roles_EXT_SearchRQ) is a Sabre Profiles User Roles web service to search roles and permission codes. Go to documentation

Update Role (Roles_EXT_UpdateRQ) is a Sabre Profiles User Roles Web service to update roles with permission codes. Go to documentation

Add Accounting Line (AddAccountingLineLLSRQ) is used to add manual accounting lines into a Passenger Name Record (PNR). Manual accounting lines for utilized invoicing purposes. Go to documentation

Add Arrival Unknown Segment (ARUNK_LLSRQ) is used to add arrival unknown segments (ARUNK) into the passenger name record (PNR). Go to documentation

Add Itinerary Info (TravelItineraryAddInfoLLSRQ) is used to add basic passenger-related content into a Passenger Name Record (PNR). This service can also be used to update an existing PNR. Go to documentation

Add Itinerary Remark (AddRemarkLLSRQ) is used to enter information into the remarks section of a Passenger Name Record (PNR). Go to documentation

Add Special Service (SpecialServiceLLSRQ) is used to send a wide variety of teletype messages to carriers. The service supports all standard interline passenger procedures, or SIPP codes. Go to documentation

Build Invoice and Itinerary (InvoiceItineraryLLSRQ) is used to generate invoices and itineraries. Go to documentation

Build Profile from Itinerary (ProfileFromReservationRQ) is used to create a Profile from a PNR (Itinerary) present in an active session. The itinerary doesn’t need to have a PNR Locator assigned, which allows the user to create a profile before End Transaction is used. Go to documentation

Delete Special Service (DeleteSpecialServiceLLSRQ) is used to remove one or more Other Supplementary Information (OSI) or Special Service Request (SSR) messages from a Passenger Name Record (PNR). Go to documentation

Divide Itinerary (TravelItineraryDivideLLSRQ) is used to divide an existing Passenger Name Record (PNR). Go to documentation

End Transaction (EndTransactionLLSRQ) is used to complete and store changes made to a Passenger Name Record (PNR). Go to documentation

Get Itinerary (TravelItineraryReadRQ) service is used to retrieve and display a passenger name record (PNR), and is the next generation of the TravelItineraryReadLLSRQ service. Go to documentation

Get Itinerary History (TravelItineraryHistoryLLSRQ) is used to retrieve historical information for a specific Passenger Name Record (PNR). Go to documentation

Get Itinerary Reports (Trip_ReportsRQ) allows the user to reports for flight based on the BSF, BSR, BST and BGR reports. The Response includes inventory, ticketing and booking data. Go to documentation

Ignore Transaction (IgnoreTransactionLLSRQ) is used to ignore a transaction. This action removes any changes made since the last time a record was ended. Go to documentation

Modify Itinerary (TravelItineraryModifyInfoLLSRQ) is used to modify or delete passenger-related content in an existing Passenger Name Record (PNR). Go to documentation

Modify Itinerary Remark (ModifyRemarkLLSRQ) is used to modify remark-related information within a Passenger Name Record (PNR). Go to documentation

Passenger Details (PassengerDetailsRQ) is used to display a PNR, or create a PNR by adding traveler information for a maximum of 99 travelers, or you can add remarks and SSRs to an existing PNR and travelers. A group can also be added. Go to documentation

Reconfirm Reservation (ResReconfirmLLSRQ) is used to re-confirm vehicle and hotel itinerary segments. Go to documentation

Retrieve Itinerary (getReservationRQ) allows an Airline or Agency to retrieve the PNR data in STL or OTA format. This service allows the user to select Stateless, Stateful, and Trip options. Go to documentation

Search for Itineraries (Trip_SearchRQ) is used to search for PNRs by many different criteria. It is the equivalent of the Sabre *-name command . Go to documentation

Update Itinerary (UpdateReservationRQ) offers functionality to allow the Airline or Agency to update Logical Records (Lrec) in particular PNR using Name and Segment Associations. Go to documentation

Verify Itinerary Address (AddressVerificationLLSRQ) is used to verify an address associated with a particular credit card. Go to documentation

Access Queue (QueueAccessLLSRQ) is used to access a designated queue or to navigate within the particular queue. This service is used for queue remove, queue exit (ignore or end transaction), queue end and bounce forward (or backwards), queue ignore, etc. Go to documentation

Get Queue Activity (QueueCountLLSRQ) is used to display the count of messages or Passenger Name Records (PNRs) on an alphabetic, numeric, and branch queues. Go to documentation

Get Queue Count (QueueCountLLSRQ) is used to display the count of messages or Passenger Name Records (PNRs) on an alphabetic, numeric, and branch queues. Go to documentation

Place Queue Messages (QueuePlaceLLSRQ) is used to place a message or Passenger Name Record (PNR) on a designated queue. Go to documentation

Calculate Carbon Emissions (Carbon_CalculatorRQ) is used to calculate approximate amount of carbon burned in kilograms per person, per all persons and per each segment in case of air travel, hotel or car hire. Go to documentation

Change AAA (ContextChangeLLSRQ) is used to allow an authorized user application to change AAA, duty codes, or partitions within the Sabre ® host system. This service also allows an authorized user application to oversign with an alternate agent sine. Go to documentation

Generate SSO Token service (SSO_GenerateTokenRQ) is used to generate tokens (SAML2.0) to provide SSO capabilities. Token represent user identity and can be passed to various systems to authenticate user. Go to documentation

Manage SSO Configuration (SSO_ManageEntityProviderRQ) is used to manage SSO Services configuration. It allows customers to create/update/delete their SSO configuration. Go to documentation

Validate SSO Token (SSO_ValidateTokenRQ) is used to validate tokens (SAML2.0, Siteminder, OpenAM) to provide SSO capabilities. Token represent user identity. ValidateToken service check if token is valid and returns user attributes stored in this token. Go to documentation

Close Session (SessionCloseRQ) is used to close a SOAP API session. This service is required to close connections because it properly cleans up the session and releases all resources allocated behind the scenes. Go to documentation

Create Session (SessionCreateRQ) is utilized to initiate a SOAP API session. Security credentials, consisting of a username, password, organization, and domain are required to connect. Go to documentation

Designate Printer (DesignatePrinterLLSRQ) is used to designate/undesignate printers for printing tickets, boarding passes, hard copies, invoices and itineraries, lists and labels, mini itineraries, or reports by specifying a line address. Go to documentation

Get Currency Conversion (DisplayCurrencyLLSRQ) is used to retrieve conversion information for all currencies loaded into the Sabre® global distribution system (Sabre® system). Go to documentation

Refresh Session (OTA_PingRQ) is used to refresh a SOAP API connection by resetting the connection's timestamp, thereby preventing the connection from being closed due to inactivity. Go to documentation

Validate Session (SessionValidateRQ) is used to verify security credentials or login information used to create or to refresh a SOAP API connection by resetting the connection's timestamp, thereby preventing the connection in the connection pool from timing out. Go to documentation

Docs Navigation