TABLE OF CONTENTS

OrderChange

The OrderChange interface is primarily used by sellers to submit modification requests for a ticket after it has been issued. It currently supports four main types of changes: changing the flight time (itinerary), adding ancillary services, processing refunds, and updating passenger names. This interface allows sellers to manage and confirm post-booking modifications on behalf of their customers


VersionDateDescription of Edit
V1.02025/10/22Initial Commit



Request Details
Path/api/flight/connectivity/order/orderChange


Request Payload Example


Request Payload Example
{
"order": {
"supplierOrderId": "917603570358296701"
},
"changeOrderChoice": {
"changeFlightTime": {
"requotedOffer": {
"offerId": "80f30d04cf6a48e2a0eaec0969851747"
}
}
},
"payment": {
"amount": "352.06",
"paymentCurrency": "CNY"
}
}


Request Payload Structure


KeyParentTypeMandatory/OptionalDescription
orderrootObjectM
supplierOrderIdorderStringM
gdnOrderIdorderStringO
changeOrderChoicerootObjectMThis object contains the specific change operation to be performed.
Only one type of change can be requested per API call. The options are mutually exclusive.
addServiceschangeOrderChoiceObjectOContainer for adding ancillary services to the booking
serviceOrdercreateOrderArrayOList of services to be added
serviceOfferIdserviceOrderStringMThe unique identifier of the service offer obtained from the serviceList or seatAvailability response
serviceTypeserviceOrderStringMThe category type of the ancillary service being ordered:
  • Baggage
  • Meal
  • PriorityBoarding
  • SpecialAssitance
  • SeatSelection
  • SportEquipment
totalAmountserviceOrderStringO
currencyserviceOrderStringO
sellerOrderNumberserviceOrderStringOSeller order number that generated in external seller system
paxIndexserviceOrderStringMThe index number of the passenger (from the paxList array) to whom this service applies.
serviceTripserviceOrderObjectM
onwardTripeligibleTripsObjectO
segmentSequenceonwardTripArrayOSegment sequence numbers in the onward trip that this service applies to
returnTripeligibleTripsObjectO
segmentSequenceonwardTripArrayOSegment sequence numbers in the return trip that this service applies to
serviceLegserviceOrderObjectO
legSequenceeligibleLegStringO
dataserviceOrderObjectO
baggageAssociationsdataObjectOThis node is ONLY present when serviceType = 'BAGGAGE'.
Contains baggage-specific details.
Same baggageAssociations object with serviceListRS
seatdataObjectOSame seat object with seatAvailabilityRS
updatePassengerchangeOrderChoiceObjectOContainer for updating passenger information
updatePassengerNameupdatePassengerArrayO
paxIndexListupdatePassengerNameStringMIndex of the passenger to update. This should be get from orderRetrieve
originalPassengerNameupdatePassengerNameObjectMCurrent passenger name details
givenNameoriginalPassengerNameStringM
surNameoriginalPassengerNameStringM
middleNameoriginalPassengerNameStringO
requestedPassengerNameupdatePassengerNameObjectMNew passenger name details
givenNamerequestedPassengerNameStringM
surNamerequestedPassengerNameStringM
middleNamerequestedPassengerNameStringO
changeFlightTimechangeOrderChoiceObjectOContainer for changing flight time or itinerary. Used when requesting a schedule change to a different flight
requotedOfferschangeFlightTimeArrayM
offerIdrequotedOfferStringMThe unique offer ID obtained from the previous flight change search OrderReshopReprice operation. This identifies the specific new flight itinerary being selected
transInforequotedOfferStringO
paxIndexListrequotedOfferArrayOList of passenger indexes (from orderRetrieve) who will be changing flights.
If not provided, the change applies to all passengers on the booking.
refundchangeOrderChoiceObjectOContainer for refund requests
refundEstimationIdrefundStringOReference ID from a prior refund estimation request. This field should only be provided when using the two-step refund process (estimation followed by actual refund request). Leave as empty when doing a direct refund. 
refundTyperefundIntMType of refund: 
  • 0: voluntary
  • 1: involuntary
refundRequestrefundArrayO
paxListrefundRequestArrayM
paxIndexpaxListStringMPassengers who you want to refund
refundTriprefundRequestObjectMTrip details for refund.
journeySequencerefundTripArrayMJourney sequences to refund 
  • 1: outbound trip
  •  2: inbound trip
refundTorefundStringOSpecifies the destination method for the refund. This field indicates how the refund amount should be returned to the seller.
The available refund methods are strictly dependent on the supplier's or airline's supported refund options. The value provided in this field must be one of the specific methods supported by the relevant carrier for this particular ticket and fare type.
  • originalFop
  • Voucher
  • points
pointsRecipientrefundObjectOContainer for loyalty program recipient information. This node is only required when refundTo is set to points
paxIndexpointsRecipientStringM
loyaltyProgramAccountpaxListObjectO
accountNumberloyaltyProgramAccountStringO
carrierloyaltyProgramAccountStringO
programNameloyaltyProgramAccountStringO
programCodeloyaltyProgramAccountStringO
paymentrootObjectOThe payment must match one of the supplier accepted payment methods 
amountpaymentStringMAmount to be charged to this payment method
paymentCurrencypaymentStringM
paymentGatewaypaymentStringO
paymentMethodpaymentObjectO
paymentCardpaymentMethodObjectOWhen the payment method is cash, this node does not need to be completed
cardBrandCodepaymentCardStringMFor example: 
  • Visa
  • Master
cardNumberpaymentCardStringMCredit card number
cardSecurityCodepaymentCardStringMCard CVC/CVV number
cardTypepaymentCardStringMFor example: 
  • Visa
  • Visa-debit
  • Visa-connect-debit
  • Mastercard
  • Mastercard-debit
cardHolderNamepaymentCardStringMName of cardholder, as it appears on the card
expirationDatepaymentCardStringMCard expiration time
YYYY-MM-DD
payerpaymentObjectOWhen the payment method is card, this node is mandatory
payerNamepayerObjectO
givenNamepayerStringM
surNamepayerStringMFamily/Lastname of the Pax
middleNamepayerStringO
phonepayerObjectO
contactTypeTextphoneStringORecommended for indicating the payer type, such as below value:
  • Passenger
  • OTA
phoneNumberphoneStringO




Response

orderChange return the same OrderView structure that is produced by orderCreate; no new fields are introduced, so the payload layout documented for the response applies unchanged to this endpoints