Getting to Production in a Few Easy Steps

Getting Started with our API Integration is easier than it seems. The very first step in this process is to make sure you've signed and returned our service agreement. Once that’s done, you can get started with the integration. To go live, just follow the 7 steps that we've laid out here. Each step includes a stage owner, the person at your company that is responsible for each task. It's easiest if the stage owner is assigned to the task in advance, so everyone knows what they have to do. Plus, if you've got a whole team working on the integration, it'll be that much easier! 

If you'd like to get a full tour of Trip Ninja and all its features, schedule a demo and we'll give you an overview of the most relevant and up-to-date features. 

  • By the end of step 3: you'll be ready to start integrating 
  • By the end of step 6: You'll be ready to go live

The Steps to Set up Success

  1. Emulation
  2. Send us your IPs to WhiteList
  3. Schedule your kickoff call
  4. Get started on pre-production
  5. Integration
  6. Certification
  7. Go Live

Wait - what's an API? 

An Application Programming Interface (API) is a set of functions and procedures that allow for communication between an application and an operating system -- in other words, it’s a means of allowing our software to communicate with your existing technology without either party having full access to the other’s information. Integrating via API is a simple, streamlined process that can be taken step by step. 

Trip Ninja uses a REST API with requests and responses in JSON format. There are five endpoints: search, price confirmation, booking/PNR creation, ticket issuing, and cancellation.

For more on what a Rest API is and how it works, see our article: Overview of a Rest API

Step 1 - Emulation

Emulation access refers to the process by which Trip Ninja gains access to the fares and information that your company has through your GDS. It allows Trip Ninja to search all of the fares that you have access to in order to provide your customers with the best fares possible. 

Stage Owner: Business leader

This process follows a few different steps depending on your GDS. 

For Amadeus: 

  1. In order for Trip Ninja to access your fares from Amadeus, we'll need to certify with them as an external developer. 

For Travelport:

  1. If you use Galileo or Apollo, you first fill out and submit the SBVC form, which gives Trip Ninja’s service bureau access to your PCC. 
  2. If you're using Worldspan, we'll need KYA commands to complete your emulation. 
You can find the Service Bureau Access form here: SBVC Form

For Sabre: 

If you're on Sabre, please reach out to our team. We'll be able to provide more details! 

If you need more information emulation or for troubleshooting information, check out our article on emulation.

Step 2 - Send us your IPs to Whitelist

Stage Owner: Technical team

To ensure everything is secure, we'll need a list of all IPs that you'll be using to access our API. A static API is preferable, but we can whitelist as many as you need if necessary. Just send these to your technical POC or your account manager and we'll sort the rest out.

Step 3 - Kickoff Call 

Stage Owner: Business and Technical Leaders

It's crucial that all stakeholders (business leader, the development point of contact, and the developer who will be performing the integration) are in on the call so that all parties are on the same page and there are no delays.

For a list of what we typically cover in this meeting see: Project Kickoff Meeting

Step 4 - Pre-Production Environment 

Stage Owner: Technical Team

After your kick-off call, you'll be provided with the URL to access the pre-production environment (this is where those API credentials come in). We use the pre-production environment to conduct testing so that you can see if the connection is working without disrupting access for anyone else. 

Trip Ninja uses Basic Authentication standards. When you open the pre-prod URL in whatever program you're using, simply encode your username and password string (“USERNAME:PASSWORD”) using base64 and pass it in the authorization headers. Here’s a python example: 

Step 5: Integration

Stage Owner: Technical Team

During the integration phase, our team will be on call to support your team. If there's a large timezone difference, we may be able to shift our working hours to give you that extra hand. To help with integration, you can refer to the documentation that our dev team has put together. 

Our API docs can be found here: API Documentation

Step 6 - Certification Testing Scenarios 

Stage Owner: Technical Team

First, we’ll give you a list of certification testing scenarios to run to ensure that you get the proper responses. Then, we’ll schedule a time to go through and check the responses and troubleshoot any issues. This is the last step before gaining access to our production environment and going live! 

Check out our Certification Testing Scenarios:  Certification Testing Scenarios

Step 7: Go Live!

Stage Owner: Technical and Business Teams

We'll schedule a time to go live so that we can monitor traffic levels and make sure that there are no issues. Happy searching! 

Still need help? Contact Us Contact Us