General API Guidelines
1. Generate single token in a day as it is valid for 24 hours (00:00 AM to 11:59 PM), so do not call "createToken" api with every search.
Note:Only call when you get "Invalid Token".
2. Trace id is valid for 15 Minutes only.
3. In case of Domestic return both result indexes OB and IB will come in Search response and similarly all methods should be called for first OB and then IB, respectively 2 PNRs will be generated for outbound and inbound journey.
4. In case of International return result index OB will come in response and in segments details both journey details will be available(outbound, inbound).
5. Additional SSR (Meal / Baggage / Seat) can be availed in case of LCC flights only, SSR need to pass in ticket request from SSR response to avail the services. In case of GDS meal and seat will be provided free of charges if airline is providing same.SSR need to pass in Book request from SSR response to avail the services.
6. Baggage, Meal and Seat array shouldnt be passed as null, Also baggage and seat can not be taken for infant pax.
7. Meal Dynamic and Seat dynamic should be passed in array in case of LCC flights.
8. Meal and seat should be passed in string in case of Non-LCC flights.
9. Fares in ticket request should be taken from fare quote response from fare breakdown array.
10. Book and ticket method should be called only for Non-LCC airlines.
11. Ticket method is only called for LCC airlines.
12. Amount will be deducted from wallet once ticket is generated successfully. Thus there is no payment gateway implementation in API from our end, that client need to implement at their end.
13. If "IsGSTMandatory" node is received true in fare quote response then GST details need to be pass for passenger in Book/Ticket request.
14. If "RequiredFieldValidators" node is received in fare quote response then check below nodes..
"RequiredFieldValidators":
{
"IsBaggageRequired": true,
"IsMealRequired": true,
"IsSeatRequired": true
}
=>If value is True for all these three nodes then client need to select and pass all the details else booking will get failed.
15. Always check ErrorCode: 6 for Invalid Token rather checking the error message.
16. TraceId is the transaction identifier from search to book/ ticket. An individual TraceId will be unique for each booking. It is provided in Search response which needs to be passed in further API request calls.
It gets expired after booking OR gets expired after 15 minutes. So, we strongly recommend, process your booking with-in 15 minutes. In case of expiry, you will get “Your session (TraceId) is expired.” error message in response.
17.GST Validation: Always refer node of "IsGSTMandatory" in FareQuote response and if it is true then you need to pass GST details in Book/Ticket request otherwise you will receive error in response.
18.Flow Of LCC & Non LCC Booking
For LCC: Search-->FareRule-->FareQuote-->SSR(optional)-->Ticket-->GetBookingDetails.
For Non-LCC: Search-->FareRule-->FareQuote-->SSR(optional)-->Book-->Ticket-->GetBookingDetails.
19.Passport Validation: Always verify node of "IsPassportFullDetailRequiredAtBook" in farequote response if it is retruned as true that is "IsPassportFullDetailRequiredAtBook":true then it is mandatory pass below details in Book/Ticket request.
"PassportNo":"Z4337010",
"PassportExpiry":"2028-01-15T00:00:00",
"PassportIssueCountryCode":"IN"
20.Net Payable: Net Payable is the fare which is payable to supplier.
Net Payable= Offered Fare + (TdsOnCommission + TdsOnIncentive + TdsOnPLB)
21.Duplicate Booking Validation: We don't allow duplicate booking within 24 hours(for Non-LCC) even if first booking is cancelled or released.
Duplicate Booking criteria: - Sector/ Journey Dates/ Airline/ FlightNo/ Passengers are same.
For example: "ABCDE" PNR created on 04-Feb-2023 with the criteria (DEL-BKK-22Jan-AI332-Mr Raj Kumar) and if you are trying to create new booking with the same criteria between 04 to 05-Feb2023 booking date then we will not allow and give “Booking is already done for the same criteria for PNR” error in response.
22.Important Validation
If you do not get any ticket response from API, always check final booking status from Retrieve Booking method.
https://www.adivaha.com/documentations/flights-api/retrieve-booking.html
23.Search Method Validation
Invalid Date Format: Please follow 'yyyy-MM-dd' format.
Departure Date can not be less than today's date.
Total number of passenger count can not be more than 9.
From_IATACODE and To_IATACODE should not be Null.
Departure date of 2nd segment can't be less than arrival of 1st segment.
24.In staging environment all results are not possible. This is only for testing purpose. Kindly check on the below search criteria :
DEL-BOM LCC:[SG,6E,G8] GDS:[UK,AI]
DEL-DXB LCC:[SG,6E,G8] GDS:[UK,AI]