UpdateAncillaryOrder

  • Purpose: Used for suppliers to notify AeroHub of confirmation information for ancillary services, completing the order confirmation.
  • Request Method: POST
  • Interface Encryption: No
  • FareMarket Address: /supplier/v1/api/update_ancillary_order

Request Parameters

Parameter Name Type Required Description
apiKey string ✅ Unique apiKey for each supplier, representing the supplier’s identity, provided by AeroHub before interface testing.
requestId string ✅ Request ID, unique for each call in the ticketing process, 32 characters in length.
ancillaryOrderNo string ✅ AeroHub ancillary order number, corresponding to ancillaryOrderNo in the AncillaryOrderList interface request.
supplierOrderNo string ✅ Supplier’s ticket order number, associated with the ticket order of ancillary sales
ancillaryOrderStatus string ✅ Ancillary order status to be updated, ISSUED(Completed), Rejected(REJECTED) indicating ticket failure and cancellation of rejected orders.
reason string ⬜ Rejection reason, must be filled in when orderStatus is set to REJECTED.

Request Example

Issuance Success Request
{
    "apiKey": "PcrNq8964iFUkE0CyVV4bhgXXX",
    "requestId": "B2B171eAv8YTQ",
    "ancillaryOrderNo": "F1745553257834618888",
    "supplierOrderNo":"123123123111111"
    "ancillaryOrderStatus": "REJECTED",
    "reason": "Airline website malfunction"
}

Response Parameters

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

Response Example

Success-Response:

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

Error-Response

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

Notes

In cases where the returned JSON data’s code is not equal to 200 or the HTTP status code is not 200, suppliers need to retry the call to ensure successful processing of the request.

Author：AeroHub  Create time：2024-03-13 10:19
Last editor：AeroHub  Update time：2025-07-29 17:21