The client needs to go through certification process to get live access.
Step 1: Test Cases Execution - Below is the list of test cases that needs to be executed by clients at their JSON Request/ Response for these cases along with the PNR/Ticket numbers will be required for verification as part of certification process.
Step 2: Certification request by client - Client makes a certification request by providing JSON request/ response along with PNR/ticket numbers for the test cases as suggested in Step 1.
Step 3: Test Cases Verification - TBO Air API team will verify the test cases, if there is any change r required. The turnaround time for the test case verification is around 4-5 days working days
Step 4: Sign off and Live Access - On successful completion of all the above steps,TBO Air API team willprovide the sign off and share the Live access details based on the Production Process form and inform us:
Step 5: Link to Production KYC form – https://forms.office.com/Pages/ResponsePage.aspx?id=mEmKAOgbXk2WLVLzT-0pioRO4fJcu99CvNWhZL-tnAFUMkw0WkpQUE8yV0VNT0QxRFZCWEhaSDhaTi4u
Step 6: Post successful signoff - Hold a test live Non LCC PNR of any airline to ensure the integration & configuration both and inform to verify the booking. Here, we are mentioning the certification process which is mandatory for the API clients
Step 1: Test Cases Execution
Below is the list of test cases that needs to be executed by clients at their end. JSON Request/ Response for these cases along with the pnr numbers will be required
for verification as a part of the certification process. Also, please make sure that test cases should be sent to the API team Casewise rather than all test cases in a single notepad file.
[Case 1]: LCC Airline Booking - 2 Adult (OneWay - Non Stop)
[Case 2]: LCC Airline Booking - 2 Adult + 1 Child + 1 Infant (OneWay - Non Stop)
[Case 3]: LCC Airline Booking - 1 Adult + 1 Child + 1 Infant (Return - One Stop)
[Case 4]: LCC Airline Booking - 1 Adult + 1 Child + 1 Infant (One way - 1 Stop including Additional Baggage and Meal)
[Case 5]: LCC Airline Booking - 2 Adult + 1 Child + 1 Infant (Return - 1 Stop including Additional Baggage and Meal)
[Case 6]: Non LCC Airline Booking - 2 Adults (One way -Non Stop)
[Case 7]: Non LCC Airline Booking - 2 Adults + 1 Child + 1 Infant (One way - 1 Stop and Meal)
[Case 8]: Non LCC Airline Booking - 3 Adults (Return - Non-Stop)
[Case 9]: Non LCC Airline Booking - 2 Adults + 1 Child + 1 Infant (Return - 1 Stop and Meal)
[Case 10]: Verification of “Price Change” /Schedule change in Book and Ticket Non LCC airlines
[Case 11]: Verification of “InProgress” Status for LCC and Non LCC airlines
1.1 Details on execution of Cases 10(Price/Schedule Change) shared above-
* Price changes need to be handled for non LCC cases.
* For LCCs, if there’s a price change after the ticket call, we would return the failure hence no need to handle this case for LCCs
1.2 Details on execution of Cases 11(Inprogress handling) shared above-
* Since for some airlines we wouldn’t get instant confirmation hence the ticket API response would return the status as InProgress = 5
* Call the GetBookingDetail API (either set up a cron job or trigger the call of this API on manual click overthe generated PNR by the end user)
* Ticket will update in the backend (tboair.com) within 10 to 15 minutes.
* Don’t perform duplicate booking if the same booking already exists with InProgress Status.
Step 2: Test Cases Verification
TBO will verify the test cases using JSON Request/ Response and suggest, if there is any change required.
The turnaround time for the test case verification is around 4-5 working days.
Step 3: Flight API Validations
After successful verification of the test cases, client need to confirm if all the validations are implemented at their end. Below is the link to download the flight api validations-
Step 4: Sign off and Live access
On successful completion of all the above steps, TBO will give sign off and provide Live access details to the client.
It is strongly recommended that the client also completes their UAT before making the services live at their end.
Step 5: IP Whitelisting
Post successful signoff, the client needs to check the Static Public IP/ Gateway ** (Network Routing IP) with their domain service provider and share the same.
This would be the IP Address from where client's API requests would come to TBO server.
To check your routing IP or public IP/ Gateway, just go to http://cmyip.com/ or http://www.whatismyip.com/
