menu

Flight Validation

Special Fare Validation

While dealing with special fares like Super 6E or SpiceMax, the fare quote response will include below nodes

  • isseatmandatory: true
  • ismealmandatory: true

    • To avoid failure during ticket request, make sure to select free meals and free seats from the SSR response and include these in the ticket request.

    Validation Of LCC & Non LCC Flights

  • Title, First Name and Last Name are mandatory, and in case of SpiceJet Passenger Name(First + Last) must be distinct.
  • Gender is mandatory.
  • DOB of Child and Infant are mandatory.
  • Phone Number is mandatory in all type of journeys.

    • Additional Validation for LCC Flights:

    For First Passenger there are some extra checks:

  • In case of AirAsia, CountryCode & CountryName is mandatory.
  • In case of LCC, Address & Email is mandatory.

    • Validation Of LCC International Flights

  • If Source is Tru Jet or Zoom Air then space is not allowed in Last name node.
  • If Source is AirAsia and Passenger is Adult then DOB is mandatory.

    • Baggage Validation for International LCC Flights:

  • In case of Fly Dubai and all the International LCC, the free baggage should be added from the SSR response to the ticket request then only you will be able to to avail yourself with the benefit. To avail the free baggage pass baggage option with Price node 0 from SSR response.
    • For Ex: 20 kg, 30 kg and 40 kg baggage are included in the fare only, until and unless you will not select this baggage in the ticket request you will not be able to avail yourself with the same.

  • If Source is I5 in case of Domestic journey, then you need to pass node of baggage and meal which has Price 0 in Ticket request from SSR response.

    • Token ID Validation

  • The token is the identification id against login session which will be used in every API call. Each token gets expired same day at 23:59:59 IST. In case of “Invalid Token” (ErrorCode: 6) in response, please re-generate a fresh token to proceed further.

    • Note:
    1. We strongly recommend to generate a single token once in a day and don’t generate a new token in every search.
    2. And always please check ErrorCode: 6 for Invalid Token rather checking the error message.

    Trace ID Validation

  • 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.

    • SSR Validation For All Cases

  • In case of Fly Dubai and all the International LCC, the free baggage should be added from the SSR response to the ticket request then only you will be able to to avail yourself with the benefit. To avail the free baggage pass baggage option with Price node 0 from SSR response.
    • For Ex: 20 kg, 30 kg and 40 kg baggage are included in the fare only, until and unless you will not select this baggage in the ticket request you will not be able to avail yourself with the same.

  • In case of return sector, if you need baggage only for one segment in that case you need to add both the objects for inbound and outbound in an array format.

    • Fare Validation

  • Base fare and tax from fare breakdown array(FareQuote response) should be divided by pax count and then pass in ticket or book request. For example if Base Fare received is 1000 and passenger count is 2 then divide 1000 by 2 and then pass 500 for each passenger in ticket request same process need to be followed for the Tax node.
  • Fare calculation should be done as per the provided formulas for Published Fare & Offered Fare(including GST).

    Price and Cancellation Change Validation:

  • Price verification is done before creating a booking/ ticket and PNR No. is returned in case of a successful booking. In case of Price change or Time change, you will get new fare and/or new time in Book response with IsPriceChanged node and/or IsTimeChanged node set as ‘true’. The price comparison is to be made at the client’s end, and Book request needs to be sent again with the updated fare and/ or updated time. If received ispricechanged: true in the farequote response than update price should be pass in book and ticket. If received ispricechanged: true in the book method responsethan in the ticket request, ispricechangedaccepted: true in the ticket request. If received ispricechanged: true in the ticket response than client need to call ticket method again by passing ispricechangedaccepted: true in the ticket request.
  • Cancellation Charges will be according to the Updated Price.

    • Flight Information Change:

  • In the farequote response if any information change such as baggage, time or any other details then you will get the node FlightDetailChangeInfo, after that you need to create the booking with the updated info. Example "FlightDetailChangeInfo": "Time" "FlightDetailChangeInfo": "Baggage".

    • 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.

    • Pax Details Validation

  • Below are the valid titles which are acceptable in Navitaire 4X(SG)

  • Passenger first, middle or last name should not have the special character like (. , / ) ( EXP: Mr Pushaan .. Grover..)

    • Passenger Title
    Male MR
    Female MRS,MS
    Child MR,MS
    Infant MSTR,MR,MS

    International Booking Validation

  • When SpiceJet is going to Dubai, Riyadh or Sharjah , then Passport is mandatory for all types of passenger.
  • If there is any LCC like SpiceJet and Indigo(except Bhutan Airlines) going to Nepal, then Passport is mandatory for Adult and Child.
  • In case of GDS, Passport is mandatory for Adult and Child(except for Nepal).
  • For FlyDubai, Passport is mandatory for all types of Passenger.

    • 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.

    Response Timeout Benchmarking/ Recommendations

    Search Method:

    Domestic (India) Response Time:
  • The 75th percentile tops out at about 5 seconds (75% is processed within 5 seconds)
  • The 95th percentile tops out at about 10 seconds (95% is processed within 10 seconds)
  • and above on 95th percentile, reqeust is processed within 30 seconds

    • International Response Time:
  • The 75th percentile tops out at about 10 seconds (75% is processed within 10 seconds)
  • The 95th percentile tops out at about 30 seconds (95% is processed within 30 seconds)
  • and above on 95th percentile, reqeust is processed within 60+ seconds

    • Book/ Ticket Method:

  • Response time lies between 30 – 60 seconds, but sometimes, response time extends till 300 seconds depending on supplier response. So, we strongly recommend to setup timeout of 300 seconds at your end to avoid financial losses.

    • Note: In case of timeout in Book/ Ticket methods, we recommend to follow below steps to make sure booking is done or not (rather than creating new booking):
  • Call GetBookingDetails() method to fetch current booking details/ status, and if you get “Your request could not be processed as booking under process.” message in GetBookingDetails() response, you will have to keep calling GetBookingDetails() method in 10-15 seconds of interval till you don’t receive actual booking details/ status to avoid financial losses.
  • Please check your booking/ ticket queue to confirm booking details to avoid financial losses.

    • Rest of the Methods:

  • Response time lies between 5 – 10 seconds, but sometimes, response time extends till 60 seconds depending on supplier response. So, we recommend to setup timeout of 60 seconds at your end to avoid failures.

    • Flow Of LCC & Non LCC Booking

  • Below is the flow of passing request in Air API-

    • For LCC
    Search-->FareRule-->FareQuote-->SSR(optional)-->Ticket-->GetBookingDetails.

    For Non-LCC
    Search-->FareRule-->FareQuote-->SSR(optional)-->Book-->Ticket-->GetBookingDetails.

    Search & Book URL Validation

  • Search and Book Url's are different so use each Url's accordingly for each method. For example refer below Url's-

    • Search URL: "http://api.tektravels.com/BookingEngineService_Air/AirService.svc"
    Book URL: "http://api.tektravels.com/BookingEngineService_AirBook/AirService.svc"

    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",
    "PassportIssueDate":"2022-04-18T00:00:00",
    "PassportIssueCountryCode":"IN"

  • Always verify node of "IsPassportFullDetailRequiredAtBook" in farequote response if it is retruned as true that is "IsPassportFullDetailRequiredAtBook":false then it is mandatory pass below details in Book/Ticket request.

    "PassportNo":"Z4337010",
    "PassportExpiry":"2028-01-15T00:00:00",
  • All the bookings either it is created on test or live environment, please pass valid Passport Details in case of Air India International Bookings in API Book Method.

    • Search Method Validation

  • Invalid Date Format: Please follow 'yyyy-MM-ddTHH:mm:ss' format.
  • Departure Date can not be less than today's date.
  • Invalid Departure Time in 1st segment: Please follow one of the time format from AnyTime - '00:00:00', Morning - '08:00:00', AfterNoon - '14:00:00',      Evening - '19:00:00', Night - '01:00:00' list.
  • Total number of passenger count can not be more than 9.
  • Origin and Destination should not be Null.
  • Multiple sources not allowed in case of SpecialReturn.
  • Departure date of 2nd segment can't be less than arrival of 1st segment.