UpdateOrder

  • Purpose: Used by suppliers to notify AeroHub of ticketing information and complete ticketing
  • Request: POST
  • Encryption: No
  • FareMarket address:/supplier/v1/api/update_order

Request

Parameter Name Type Required Description
apiKey string ✅ Each supplier has its own unique apiKey, which is used to indicate the supplier’s identity. AeroHub provides it to the supplier before interface testing.
requestId string ✅ Request ID, which is unique for each call in the ticket issuance process and has a length of 32 digits.
purchaseOrderNo string ✅ The order number of AeroHub corresponds to the OrderNo when requesting the Order interface.
orderStatus string ✅ Order status that needs to be updated, TICKETED has been issued, TICKETED, REJECTED has rejected the order
sourceType int ⬜️ The source of the calling interface, AeroHub’s own field, 1 is called through API, 2 is called through supplier background, default 1
reason string ⬜️ The reason for order rejection must be filled in when orderStatus is assigned the value REJECTED. Please refer to the examples: Incorrect information; Withdraw before issuing; Duplicate booking; Fare change; Flight sold out; Ancillary not available; Airline error; Payment card error; Automatic ticketing failed
ticketNoItems array/ticketNoItems Element ⬜️ Ticketing information needs to be true and valid, and can be used for reservation management and guest check-in on the airline’s official website. It is required when orderStatus is assigned the value TICKETED.

array/ticketNoItems Element

Parameter Name Type Required Description
passengerName string ✅ Passenger name, separated by / between last name and first name, LastName/FirstName MiddleName
flightNumber string ✅ Flight number, such as: CA123
cardNo string ✅ ID number, maximum 15 characters
pnrCode string ✅ You can manage the coding of booking information on the airline’s official website, such as airline PNR or low-cost airline PNR.
ticketNo string ✅ Ticket number, if there is no low-cost airline, it can be consistent with PNRCode
segmentNo int ✅ Flight sequence, 1 outbound trip, 2 return trip
sequence int ✅ The sequence of flight segments starts from 1. Note: If it is a round trip, both the outbound and return journeys start from 1.
depAirport string ✅ Departure airport code, using IATA three-letter code as the standard
arrAirport string ✅ Arrival airport code, using IATA three-letter code as the standard
ticketingTime int ✅ The real time when the supplier issued the ticket, used for traceability, in timestamp format, with a length of 10 digits (accurate to the second level)
accountName string ⬜️ The account registered when issuing tickets on the airline’s official website, used for booking management
accountPass string ⬜️ The password for the account registered when issuing tickets on the airline’s official website is used for booking management.
contactName string ⬜️ The contact person reserved by the supplier when issuing tickets, used for customer after-sales or quality inspection, separated by / between the first and last name, LastName/FirstName MiddleName
contactEmail string ⬜️ The email address reserved by the supplier when issuing tickets, used by customers for after-sales or quality inspection
contactMobile string ⬜️ The mobile phone number reserved by the supplier when issuing tickets is used by customers for after-sales or quality inspection

Sample Request

Ticket issuance request successful

{
    "apiKey": "PcrNq8964iFUkE0CyVV4bhgXXX",
    "requestId": "B2B171eAv8YTQ",
    "purchaseOrderNo": "F1745553257834618888",
    "orderStatus": "TICKETED",
    "sourceType": 1,
    "reason": "",
    "ticketNoItems": [{
        "passengerName": "ZHANG/SAN",
        "flightNumber": "LA2407",
        "cardNo": "166341242",
        "pnrCode": "LT75TO",
        "ticketNo": "LT75TO",
        "segmentNo": 1,
        "sequence": 1,
        "depAirport": "VVI",
        "arrAirport": "LIM",
        "ticketingTime": 1705026483,
        "accountName": "",
        "accountPass": "",
        "contactName": "ZHANG/SAN",
        "contactEmail": "zhang@gmail.com",
        "contactMobile": "+8615001230000"
    }]
}

Response

Parameter Name Type Required Description
code int ✅ For the status code of AeroHub, refer to Market Errors in the general instructions.
msg string ✅ For AeroHub error instructions, refer to Market Errors in General Instructions.

Response Example

Success Response:

{
    "code": 200,
    "msg": "Successful"
}

Error Response

{
    "code": 400,
    "msg": "Failed"
}

Things to note

  • When encountering the returned JSON data code When not equal to 200 or the HTTP status code is non-200, the provider needs to retry the call to ensure successful processing of the request.
Author：AeroHub  Create time：2023-07-10 16:15
Last editor：AeroHub  Update time：2026-10-20 11:28