DerbySoft GDN Seller API

TABLE OF CONTENTS

ConfirmOrder

ConfirmOrder

This API provides the capability for sellers to confirm an unticketed order (‘HOLD’ status) by providing payment information

Version	Date	Description of Edit
Beta	2025/09/16	Initial Commit
v1.0	2025/10/22	ConfirmOrderRQ: Add gdnOrderId/gdnBookingId

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

Request Payload Example

Request Payload Example

{
   "confirmOrder": {
       "payment": {
           "amount": "1961.67",
           "paymentCurrency": "USD"
       },
       "order": {
           "supplierOrderId": "917609440975591701"
       }
   }
}
}

Request Payload Schema

Key	Parent	Type	Mandatory/Optional	Description
confirmOrder	root	Object	M
order	confirmOrder	Object	M
supplierOrderId	order	String	M
gdnOrderId	order	String	O
flightOrder	confirmOrder	Object	O
payment	root	Object	O
amount	payment	String	M	Amount to be charged to this payment method
paymentCurrency	payment	String	M
paymentGateway	payment	String	O	Enumeration: Direct: pay directly to airline/suppliers DSPAY: 3rd party payment service
paymentMethod	payment	Object	O
paymentCard	paymentMethod	Object	O
cardBrandCode	paymentCard	String	M
cardNumber	paymentCard	String	M	Credit card number
cardSecurityCode	paymentCard	String	M	Card CVC/CVV number
cardType	paymentCard	String	M	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
payer	payment	Object	O
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
phoneNumber	phone	String	O
promotionCriteria	root	Object	O	A Promotion and discount code criteria to be passed to the retailer airline that could influence returned offers
promotionCode	promotionCriteria	String	O	Promotion code ID or number

Response

confirmOrder 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