First Client need to go through the API Sample verification process.
For which client will submit one sample case as advised in Sample Verification section,
make all the changes as per the API team suggestion. Once, sample is successfully verified then client will submit the below mentioned test cases(1-5 Mandatory, Rest as per the requirement).
API Client can check all the details in Sample Verification section and in API Guide.
Please check below Certification Process steps-
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]: GDS Domestic Oneway – 1 Adult
[Case 2]: LCC Domestic Oneway – 1 Adult + 1 Child + 1 Infant (With SSR)
[Case 3]: LCC Domestic Return – 2 Adults + 2 Child + 1 Infant
[Case 4]: LCC International Oneway – 1 Adult + 1 Child + 1 Infant (With SSR)
[Case 5]: GDS International Return – 2 Adults + 2 Child + 1 Infant
Additional Cases (As per the Requirement):
[Case 6]: LCC Domestic Special Return – 2 Adult + 1 Child
[Case 7]: GDS Domestic Special Return SSR – 2 Adults + 2 Child + 1 Infant
[Case 8]: GDS Multiway – 2 Adults
[Case 9]: Domestic Oneway Air Fare Calendar - 2 Adults
[Case 10]: GDS Advance Search (PriceRBD) Booking – 2 Adults
[Case 11]: NDC International Oneway- 2 Adult+ 2 Child(With SSR)
[Case 12]: NDC International Return- 2 Adult+ 2 Child
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/