DerbySoft GDN Seller API

TABLE OF CONTENTS

Request Payload Example

Request Payload Structure
Response

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

Version	Date	Description of Edit
V1.0	2025/10/22	Initial Commit
V1.1	2025/11/23	Added display for freshbooking with bundle in orderChange response
V1.2	2026/03/17	Added documentsId to relevant order change requests in OrderChange API Added new context fields (refundRemark, duplicatedWith) for refunds in OrderChange API Standardized enumeration for refund reasons to ensure data consistency in OrderChange API
V1.3	2026/04/23	OrderView: Return GST related field in contactInfos node. Response with richer modification history
V1.4	2026/07/02	Added post-booking ancillary modification history for ADD_ANCILLARY. OrderView returns servicePsgFares under orderView.serviceInfos and supports totalWeightMeasure under baggage weightAllowance.
V2.0	2026/08/15	OrderChange RQ: Supported SSR baggage/service upgrades (ssrUpgrade). Supported post-booking seat reassignment (seatReassignment). Added Multi-FOP payment methods (WALLET, CARD, BSP_CASH, etc.). Supported post-exchange ancillary additions and document uploads (supportingDocuments). OrderViewRS: Aligned response schema with orderCreate RS The returned flight offer now includes promotionDetailInfo under totalPrice and passenger fare price when a promotion was applied to the order.

Request Details
Path	v1.0	/api/flight/connectivity/order/orderChange
Path	v1.1	/api/flight/connectivity/order/V1.1/orderChange
Path	v1.2	/api/flight/connectivity/order/V1.2/orderChange
Path	v1.3	/api/flight/connectivity/order/V1.3/orderChange
Path	v1.4	/api/flight/connectivity/order/V1.4/orderChange
Path	v2.0	/api/flight/connectivity/order/V2.0/orderChange

Request Payload Example

{
   "order": {
       "supplierOrderId": "101522924132221190144",
       "gdnOrderId": "326100900041998261"
   },
   "changeOrderChoice": {
       "changeFlightTime": {
           "requotedOffer": {
               "paxIndexList": [
                   "1"
               ],
               "offerId": "107ed637385b4046b51a33f1c995b1b8"
           }
       }
   },
   "payment": {
       "amount": "40.21",
       "paymentCurrency": "USD"
   }
}

Request Payload Structure

Key	Parent	Type	Mandatory/Optional	Description
order	root	Object	M
supplierOrderId	order	String	M
gdnOrderId	order	String	O
changeOrderChoice	root	Object	M	This 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.
addService	changeOrderChoice	Object	O	Container for adding ancillary services to the booking
serviceOrders	addService	Array	O	List of services to be added
serviceOfferId	serviceOrders	String	M	The unique identifier of the service offer obtained from the serviceList or seatAvailability response
serviceType	serviceOrders	String	M	The category type of the ancillary service being ordered： Baggage Meal Priority Boarding Special Assistance Seat Sport Equipment Carbon Offset
totalAmount	serviceOrders	String	O
currency	serviceOrders	String	O
sellerOrderNumber	serviceOrders	String	O	Seller order number that generated in external seller system
paxIndex	serviceOrders	String	M	The index number of the passenger (from the paxList array) to whom this service applies.
serviceTrip	serviceOrders	Object	M
onwardTrip	serviceTrip	Object	O
segmentSequence	onwardTrip	Array	O	Segment sequence numbers in the onward trip that this service applies to
returnTrip	serviceTrip	Object	O
segmentSequence	returnTrip	Array	O	Segment sequence numbers in the return trip that this service applies to
serviceLeg	serviceOrders	Object	O
legSequence	serviceLeg	String	O
data	serviceOrders	Object	O
baggageAssociations	data	Object	O	This node is ONLY present when serviceType = 'BAGGAGE'. Contains baggage-specific details. Same baggageAssociations object with serviceListRS
seat	data	Object	O	Same seat object with seatAvailabilityRS
updatePassenger	changeOrderChoice	Object	O	Container for updating passenger information
updatePassengerNames	updatePassenger	Array	O
paxIndex	updatePassengerNames	String	M	Index of the passenger to update. This should be get from orderRetrieve
originalPassengerName	updatePassengerNames	Object	M	Current passenger name details
givenName	originalPassengerNames	String	M
surname	originalPassengerNames	String	M
middleName	originalPassengerNames	String	O
requestedPassengerName	updatePassengerNames	Object	M	New passenger name details
givenName	requestedPassengerName	String	M
surname	requestedPassengerName	String	M
middleName	requestedPassengerName	String	O
documentsId	updatePassengerNames	Array	O	Added in v1.2 Associates supporting documents with the request, field available, but upload interface not yet released
changeFlightTime	changeOrderChoice	Object	O	Container for changing flight time or itinerary. Used when requesting a schedule change to a different flight
requotedOffer	changeFlightTime	Object	M
offerId	requotedOffer	String	M	The unique offer ID obtained from the previous flight change search OrderReshopReprice operation. This identifies the specific new flight itinerary being selected
transInfo	requotedOffer	String	O
paxIndexList	requotedOffer	Array	O	List of passenger indexes (from orderRetrieve) who will be changing flights. If not provided, the change applies to all passengers on the booking.
documentsId	changeFlightTime	Array	O	Added in v1.2 Associates supporting documents with the request, field available, but upload interface not yet released
refund	changeOrderChoice	Object	O	Container for refund requests
refundEstimationId	refund	String	O	Reference 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.
refundType	refund	Int	M	Type of refund: 0: voluntary 1: involuntary
refundReason	refund	Int	O	Type of refund reasons: 0: personal reason 1: illness reason 2: schedule change reason 3: visa refusal 4: double payment 5: duplicate booking 6: korea voluntary cancellation 7: indonesia domestic voluntary cancellation 8: united states voluntary cancellation 9: flight cancellation 10: deceased guest 11: connecting flight affected 12: other Note: for the specific refund reasons supported by each airline, please refer to the ‘Refund’ section in the Order Servicing Process part.
refundRequest	refund	Object	O
paxList	refundRequest	Array	M
paxIndex	paxList	String	M	Passengers who you want to refund
refundTrip	refundRequest	Object	M	Trip details for refund.
journeySequences	refundTrip	Array	M	Journey sequences to refund 1: outbound trip 2: inbound trip
refundTo	refund	String	O	Specifies 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
pointsRecipient	refund	Object	O	Container for loyalty program recipient information. This node is only required when refundTo is set to points
paxIndex	pointsRecipient	String	M
loyaltyProgramAccount	pointsRecipient	Object	O
accountNumber	loyaltyProgramAccount	String	O
carrier	loyaltyProgramAccount	String	O
programName	loyaltyProgramAccount	String	O
programCode	loyaltyProgramAccount	String	O
refundRemark	refund	String	O	Added in v1.2 Additional comments or notes for the refund
documentsId	refund	Array	O	Added in v1.2 Associates supporting documents with the request, field available, but upload interface not yet released
duplicatedWith	refund	String	O	Added in v1.2 References the original booking PNR for duplicate case
ssrUpgrade	changeOrderChoice	Array	O	[Since v2.0]
serviceOfferId	ssrUpgrade	String	M	[Since v2.0] The serviceOfferId returned from serviceList API
paxIndex	ssrUpgrade	Array	M	[Since v2.0]
seatReassignment	changeOrderChoice	Array	O	[Since v2.0]
serviceOfferId	seatReassignment	String	M	[Since v2.0] The serviceOfferId returned from seatAvailability API
paxIndex	seatReassignment	Array	M	[Since v2.0]
payment	root	Object	O	The payment must match one of the supplier accepted payment methods
amount	payment	String	M	Amount to be charged to this payment method
paymentCurrency	payment	String	M
paymentGateway	payment	String	O
paymentMethod	payment	Object	O
paymentMethod	paymentMethod	String	O	[Since v2.0] This field indicates the settlement method used for the order. It enables the purchasing agent to explicitly choose between cash‑based (wallet / BSP settlement) and card‑based payment, or other alternative methods, when the transaction supports multiple payment channels. If empty, default will be WALLET. Enumeration List WALLET – Airline / supplier wallet (e.g., IATA EasyPay). Pre‑funded electronic wallet; funds are blocked at the time of ticket issuance. No card details are required. BSP_CASH – BSP cash settlement. The sale is reported as cash and settled via the BSP (Billing and Settlement Plan) according to IATA’s standard settlement timelines. No card details are required. CARD – Payment card (credit or debit). This value requires the PaymentCard sub‑object to be present with valid card details (e.g., card number, expiration date, cardholder name). VOUCHER – Payment using a voucher or travel certificate. BANK_TRANSFER – Payment via bank transfer (wire transfer). LOYALTY_REDEMPTION – Frequent flyer miles or loyalty program redemption. OTHER – Other payment methods not covered by the above values. This is an extensible placeholder for future additions.
paymentCard	paymentMethod	Object	O	When the payment method is cash, this node does not need to be completed
cardBrandCode	paymentCard	String	M	For example: Visa Master
cardNumber	paymentCard	String	M	Credit card number
cardSecurityCode	paymentCard	String	M	Card CVC/CVV number
cardType	paymentCard	String	M	For example: Visa Visa-debit Visa-connect-debit Mastercard Mastercard-debit
cardHolderName	paymentCard	String	M	Name of cardholder, as it appears on the card
expirationDate	paymentCard	String	M	Card expiration time YYYY-MM-DD
payer	payment	Object	O	When the payment method is card, this node is mandatory
payerName	payer	Object	O
givenName	payer	String	M
surname	payer	String	M	Family/Lastname of the Pax
middleName	payer	String	O
phone	payer	Object	O
contactTypeText	phone	String	O	Recommended for indicating the payer type, such as below value: Passenger OTA
phoneNumber	phone	String	O

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.