FAQ

General questions

Sabre® Dev Studio is a portfolio of APIs, Informational Services, Notification Services and a variety of tools. Whether you are focused on building a powerful B2B solution or the next great B2C application, we have the capabilities you are looking for. Our entire portfolio is available right here, all in one place, the Dev Studio site.
The Sabre® travel marketplace unites buyers and sellers of travel. More than 415,000 travel agents and millions of travelers shop and book travel provided by airlines, hotels, car rental outlets, rail lines, cruise lines and tour operators.
Anyone can use Sabre® Dev Studio. Whether you’re an online travel agency, a meta search site, a travel management company, an up-and-coming startup or a company wanting to integrate travel into your application, we have the capabilities you need.
We have a number of different pricing options for our services. Whether you are a company just starting out or an established travel provider, we have pricing options that will fit your business needs.
You will still have full access to all of your services and tools, they will now be here in one central location, the new Dev Studio site. Please note you will need to register a new account on this site. Please provide your Pseudo City Code (PCC) and company email address so we can make sure you get access to all of your current services.
Simply go to the contact form and choose “I want to request production credentials” in the drop down. Someone from our team will quickly be in touch to get you set up.

As a partner in our Sabre® Authorized Developer program, you will receive dedicated support, access to our Sabre Dev Studio portfolio and the opportunity to promote your products to our travel agency customers.

We are committed to having the most effective third-party developer program in the travel industry. We currently have relationships with 150+ third-party developers around the world who provide software services to meet a broad spectrum of travel agency business needs.

Visit the contact form and select the option “I want to become a Sabre customer” We will be in touch with you about next steps soon!

APIs

We recommend you be familiar with:
  • REST and JSON and/or SOAP and XML
  • Calling HTTP methods explicitly, HTTP syntax and creating HTTP headers
  • Previous experience with the Sabre travel marketplace and Sabre development tools is not necessarily needed.
You can use any language or tool of your choice, such as Java, Python, Ruby and JavaScript.
No, you can use our REST APIs independently.
The basic requirements for your application are to:
  • Make HTTP requests
  • Parse JSON documents
After you register your application and receive test credentials, you can use the API Explorer to test the APIs interactively or an API test client of your choice and point to our Sandbox (certification) environment. Today these include our REST APIs, but we are quickly expanding to include some of our SOAP APIs.
You can test your application by pointing to our Sandbox (certification) environment. Learn more about our environments. If you need access to other services in the certification environment, contact us to find out more.
The API Explorer gives you a glimpse of what you can do with our APIs. Once you are ready for production, you will get access to the full list of available domestic and international city pairs.

REST versus SOAP APIs

Though both REST and SOAP technologies can operate cross platform they are architecturally different to each other, here is some of differences between REST and SOAP:
  • REST is an architectural style unlike SOAP which is a standardized protocol
  • REST is typically more simple and easier to use than SOAP
  • REST uses native HTTP protocol for producing or consuming APIs. SOAP can support HTTP and other forms such as SMTP
  • REST is usually more lightweight with payload requests and responses compared to SOAP
  • REST is native to modern development languages such as JavaScript, Ruby, Python, and many others
  • REST is more optimized for mobile platforms
  • SOAP is more optimized for Stateful operations

For more information about REST and SOAP, start with the following:

No, there is not. Choosing between SOAP vs REST as a technology may come down to a matter of preference. It could be based on the developer skillset, application platform, infrastructure design, authentication model, and many other reasons. If you have any questions, we recommend you reach out to your Account Manager or Sabre API Help Desk.

A Sabre API that has the capability of requesting data via REST and SOAP will mostly overlap; meaning generally there should be no specific differences, since the backend services are the same. Depending on the actual service there may be certain functionality that may differ and/or was optimized for one technology. For example enhancing a REST service to be truly stateless. This is why we recommended always referencing the API documentation.

What will differ is the authentication model used for SOAP vs REST. REST authentication uses access tokens with an expiration time and is used for more stateless workflows. SOAP uses sessions that are generally tied to stateful operations. For more information on REST authentication and SOAP session Management, please refer to our API Documentation. The response format for the REST APIs Sabre exposes will be presented in JSON compared to XML for SOAP.

Generally speaking, the backend service for an API that is exposed in both REST and SOAP will be the same; users should expect similar response times and capacity allowances. In some occasions REST JSON requests and responses may be more lightweight compared to SOAP, which in combination with a simpler authentication model may drive improved performance. In other situations, existing customers that have fine tuned their current SOAP API deployment with techniques such as compression, session manager, application code improvements, and others will typically not see improvements in performance by switching technologies.
No, generally the response content from an API that is exposed in multiple technologies will be the same but with a different response format, normally JSON for REST and XML for SOAP. We recommend referencing the technical documentation of the specific API being consumed.
Simply register to get instant access. Use the API Explorer to test the REST APIs interactively or an API test client of your choice and point to our Sandbox (certification) environment. Today these include our REST APIs, but we are quickly expanding to include some of our SOAP APIs.
Generally all Sabre APIs that are exposed in multiple technologies such SOAP and REST should be at parity. For validation please reference the documentation of the specific API.

If you have not yet done so, register on the site which will get you instant access to test credentials and the API Explorer. We recommend reading the API documentation that will provide specific information about consuming the service.

For Sabre Dev Studio customers with specific capacity settings of APIs, please contact your Sabre account manager or Sabre API Help Desk.

Yes, check out the sample code section where we expose different technology sample libraries that you can reference, all hosted on gitHub.
For more information on how to consume Sabre REST APIs and authenticate visit REST basics.
Yes. We do highly recommend reading the specifics on authenticating with both technologies and not mixing access and session tokens with different service calls.
Yes, contact your regular support channels. For more information please contact your Account Manager or use the contact us section.
There are no plans to deprecate SOAP API services, we will continue to support and enhance these until further notice.
Yes, we will continue to expand both types of APIs. Continue visiting regularly for updates on new services, tools and resources.

Red App Developer Toolkit

The Sabre® Red™ App Centre is the world’s first B2B app marketplace for the travel industry. It brings travel buyers (travel agencies, travel management companies and leisure operators) and developers together to extend the power of Sabre® Red™ Workspace in a revolutionary way.

Sabre® Red™ Apps are optional, authorized applications that extend the capabilities of the Sabre Red Workspace. They plug into and become part of the Red Workspace.

Sabre Red Apps leverage the technical capabilities of the Eclipse Rich Client Platform, which is the open source software upon which the Red Workspace is built and operates. Red Apps are developed by Sabre teams or by Sabre Red App Certified Providers and are provisioned through the Sabre Red App Centre.

Any Sabre Connected agent who uses Sabre Red Workspace. Agency buyers can request an app through the Red App Centre and then activate it within their Red Workspace to customize their workflow.
Agencies or third-party developers can create unique Red Apps. They can be anyone, from anywhere, as long as they have an idea that expands the capabilities of the Sabre Red Workspace. Learn more about how to become a Sabre Red App Certified Provider.

A Sabre Red App Certified Provider is any developer who has a Red App available in the Sabre Red App Centre. In order to become a Sabre Red App Certified Provider, the developer’s application including their Red App proposal must be approved by Sabre.

After Sabre approves the developer and proposal, the developer can start creating a Red App. When Sabre certifies a developer’s first Red App, the developer becomes a Sabre Red App Certified Provider.

Adobe Flash, Java-SWING, Qik Developer, HTML, Java-SWT, Sabre Scribe, Java-AWT and JS.

First, review the overview document and download the Red App Developer Toolkit to view the capabilities and functionality for building Red Apps.

Next, visit sabreredappcentre.com and complete the application to become a Sabre Red App Certified Provider.

After your proposal is approved and your agreement is signed, you will receive access to Production and can begin developing your Red App.

Apply to become a Red App Certified Provider. During your application, you will be asked to also provide a Red App proposal. Provide detailed information about your Red App, such as the basic functionality, type of UI element, communications, security and technology that you plan to use.