Getting Started with the Native API
The Native API replaces the Sabre Emulator API, creating a bridge for an external application to connect to the new Sabre Red 360. All customers using the Emulator API must now use the Native API.
To successfully migrate, you must take the following steps:
- You must become a Red App Certified Provider.
- Within the application, you will submit a proposal for your Red App.
After submitting your proposal, you will be contacted by Sabre.
Once approved, and sign the Sabre Red App Certified Provider agreement, you will receive your Red App ID. After this, you will need to use our Sabre Red 360 Developer Toolkit to use the Native API. Getting Started is easy:
- Sign up at Dev Studio.
- Download the Sabre Red 360 Developer Toolkit.
- Download and install Eclipse IDE.
- Configure the SDK following the Getting Started Guide found under the documentation folder on the DevKit.
- Open the Eclipse zip file and navigate to: Help / Sabre Red 360 Developer Toolkit - 3.1 / Sabre Native API
Frequently Asked Questions (FAQs)
What is the new Sabre Red 360 Native API, and how does it compare to the Emulator API?
The Native API replaces the former Emulator API. It works as a bridge for an external application to connect to Sabre Red 360.
Can I continue to use the Emulator API as a standalone product?
No. The Emulator API is not compatible with the new Sabre Red 360; therefore, all current Emulator API applications must be migrated to the Native API.
Are all functionalities from the Emulator API available on the Native API?
No. Since the platform where the API resides is changing, there are some functionalities that will not be supported. For example, the Emulator API markup features Highlight and Modify, which are currently supported on Sabre Red Workspace 2.x.x but will not be available on the new Sabre Red 360.
Is there any existing Sabre Red 360-supported technology that can be used instead of the Native API?
No. The Sabre Red 360 Developer Toolkit (SDK) is all new technology provided to integrate applications with Sabre Red 360 point of sale. It provides advanced and effective integration capabilities, along with the added value of the Sabre Red App Centre Marketplace.
Are there any discrepancies between the Sabre Red 360 Developer Toolkit and the Emulator API?
With the exception of the markup features identified above (#3), the SDK contains all of the features currently available in the Emulator API.
What is the defined timeline to migrate from the Emulator API to the Native API?
The migration is directly correlated to customers that are currently using Emulator API applications on Sabre Red Workspace and are currently targeted to upgrade to the new Sabre Red 360. While these identified customers are marked for a later migration wave, we recommend developers immediately migrate their applications to the Native API.
How can developers access the Native API documentation and other resources to start testing and developing their application’s integration with the new Sabre Red 360?
You can find Native API documentation at the top of this page.
Will the Native API be exposed to both Sabre Red Workspace and new Sabre Red 360 users?
No, the Native API is only available for the new Sabre Red 360 users.
Is .NET a supported technology for the Native API? What resources are available to assist with the upgrade?
Yes, .NET is supported, among other modern development languages. We have created a sample code application to help developers understand the required steps to integrate into the ActiveMQ bridge.
Will my customer be required to place a new Sabre Red 360 Native API order, replacing the existing Emulator API amendment?
Yes. The Native API is now embedded into the new Sabre Red 360 Developer Toolkit; therefore, it is now required to submit a proposal to become a Red App Certified Provider in order to publish the application (bridge) into the Sabre Red App Centre. Instructions on how to get started with the Native API are available on Sabre Dev Studio.
Are there any costs to use the Sabre Red 360 Developer Toolkit?
No. The SDK is free for download. However, there may be associated costs depending on the application undergoing development.
Is the Native API a different technology from the Emulator API?
While Sabre’s Emulator API solution was based on a library, the Native API solution uses a messaging-based approach on open and flexible technology
My customers have technical questions about the Native API. Who can they contact?
Native API support is managed by the Sabre Red Apps support desk. Please see the below additional resources:
- Official ActiveMQ documentation is available at http://activemq.apache.org/
- Sabre Red 360 Developer Toolkit official documentation is available at https://developer.sabre.com/tools/Red_App
- For official Sabre Red 360 Developer Toolkit support, please contact: email@example.com
Why is Sabre not supporting Emulator API technology in the new Sabre Red 360?
The Native API was strategically included in the Sabre Red 360 Developer Toolkit to expand its scope. The SDK enables our current Emulator API customers to have more resources and use richer features in their applications. This technology is aligned with the broader platform strategy of the new Sabre Red 360.
My customers that utilize Emulator API today have no immediate plans to move to the new Sabre Red 360 this year. Are there any actions we should be taking?
It is highly recommended that Emulator API customers migrate to the Native API as soon as possible. However, the Emulator API will continue to be supported on Sabre Red Workspace.