menu

Air Amendment

Method Structure

Please consider below points for clarification:

  • Air Amendment is to buy baggage, meal or seat after Ticket is created. As of now special service is not included in amendment.
  • If baggage is already added for a specific pax while booking the PNR then baggage for the same pax can’t be bought through air amendment.
  • As of now air amendment is only available for LCC carriers i.e. Indigo, Spice jet, Akasa, AirIndiaExpress, AirAsia, Jazeera and FlyDubai.
  • Air Amendment can be done as many as times you want after ticketing.
  • In Amendment, Invoice will be generated per passenger.
  • If meal and baggage is bought in amendment of a passenger at the same time then the invoice will be the same for both, but if meal and baggage is bought for the same passenger but in different time then invoice of them will be different.


    • JSON

    Service URL (REST) to be used:
    http://api.tektravels.com/BookingEngineService_Air/AirService.svc/rest/SSR


    SSR Request: 

    {
    "EndUserIp": "192.168.11.195",
    "TokenId": "XXXXXXXXXXXXXXXXXXXXXXXXXX", 🡪 (Current day’s Token Value)
    "BookingId": "XXXXXXX" 🡪 (Booking ID of the PNR which is already created)
    }

    SSR Response:


    Service URL (REST) to be used:
    http://api.tektravels.com/BookingEngineService_Air/AirService.svc/rest/TicketReIssue


    Ticket ReIssue Request: 

    {
    "EndUserIp": "192.168.11.195",
    "TokenId": "381931f7-afcb-4e56-a5b5-abb6889844c7",
    "TraceId": "bc6b66e9-90c1-40e3-b9e7-577421e22aaa",
    "BookingId": 1599626,
    "SSR": [
    {
    "PaxId": 2587823, (PassengerID of the passenger for whom SSR needs to be bought)
    "Baggage": [ (BaggageArray: One of the available baggageoptions,provided in the SSR response)
    {
    "AirlineCode": "SG",
    "FlightNumber": "11",
    "WayType": 2,
    "Code": "EB10",
    "Description": 2,
    "Weight": 10,
    "Currency": "INR",
    "Price": 4950,
    "Origin": "DEL",
    "Destination": "DXB"
    }
    ] } ] }


    Ticket ReIssue Response:


  • Nodes that were earlier received in Ticket () response will be received in this response also such as PNR, Booking ID, Segment, Fare Details,       Passenger Details etc.
  • In this response, Invoice array will be received which will have all the invoices.
  • Invoices will be generated per passenger at a time, if we go for an amendment for the second time then the second time also invoices will       be generated.



  • In this response, Booking History array will be received which will have all details as provided in TBO portal.



  • SSR charges will also be received.



  • In Segment Additional Info Array, All the SSR that are bought will be provided, Baggage before pipe is free baggage provided by airline and       baggage after pipe is the purchased one.



  • In case of LCC in EMD number nodes, PNR will be received.
  • Invoice Id is the same that is received in the Invoice array for the same Amendment.