Tip: We've put together a list of common support questions from developers that you might find helpful. Just a heads-up, it’s not an all-inclusive resource. For more in-depth help, we suggest checking out our detailed guidelines and specifications. If you still need extra technical support and can’t find what you’re looking for in our docs, don’t hesitate to reach out to our friendly DerbySoft Flight Services support team at flight.prod.ops@derbysoft.net. We’re here to help!

Q: Where to find the Airport and Airline Related Information?

A: For Airport Codes and Airline Info, please refer to the IATA Website.



Q: How many passengers can be passed in the Search API at a minimum and maximum? 

A: 

  • Minimum: 1 adult. 
  • Maximum: The Sum of adult and child passengers should be equal to or less than 9. The number of infants should be equal to or less than the number of adults. If these conditions are not satisfied, then you will get errors. 


Q: For how long is the offerId valid?                        

A: offerId is Valid for 30 minutes




Q: How would I know If a Segment has connecting flights?

A: There is an element in response to segmentInfo named "stops". It has all the information for connecting stops.




Q: How can I fetch  Fare-Rule?

A: No separate API call is required to retrieve the fare rules. The fare rules are returned within the condition node under the fareComponent in the OfferPrice API response. These rules are provided in two formats: structured fare rules and text-based fare rules.    


       

                        

Q: Is Duplicate Booking Allowed In Derbysoft?                    

A: No, the system will check the same itinerary and the same passenger booked by the same agent, then the system won't allow you to create the booking for a new request. 




Q: What is the difference between supplierOrderId and gdnOrderId?

A:

  • supplierOrderId: This is the order reference or PNR provided directly by the suppliers or airlines. You can use this ID to check the booking status directly on the airline’s website or system.
  • gdnOrderId: This is an internal tracking identifier generated by our platform. It helps us link your request to the specific booking across our system, making it easier to provide support and troubleshoot issues. You will primarily use this ID when contacting our support team. 


In summary: Use the supplierOrderId for all interactions with the airline. Use the gdnOrderId when you need assistance from our support team.


Q:  How can I distinguish between the marketing carrier and the operating carrier for a flight?


A: 

You can find this information within the flightDesignator object, located under the path tripsInfo->onwardTrip/returnTrip->segmentInfos.

The logic for how the carriers are returned is as follows:

  • If the marketing carrier and the operating carrier are the same, only the marketing carrier will be returned.
  • If they are different, both the marketing carrier and the operating carrier will be returned separately within the flightDesignator object.

Simply check this node to determine whether you are viewing a codeshare flight (where the carriers are different) or not.


Q. Shall we skip selecting in-bundle seats and meals?

A.

  • B2B partners and OTAs are required to prompt customers to select their in-bundle meal and seat during the booking flow.
  • While skipping selection is technically possible, doing so forfeits these benefits. The passenger will not receive a meal on board and will not be assigned an eligible seat, despite having paid for the bundle. This inevitably leads to customer complaints and is strongly discouraged.

Q. If a selected bundle includes seats as a benefit, should the Seat Availability API return the price for those in-bundle seats as 0 when we pass the bundleOfferId in the request?

A.

Please note that inBundle service pricing is dynamic; rates may be zero, or fall above or below zero. If you select an inBundle service with a negative rate, the total bundle price will be discounted accordingly. Conversely, selecting a service with a rate above zero will be added to the bundle total.


Q. How to handle the duplicatedWith field during the refund requests for duplicate bookings, especially in scenarios with multiple duplicate bookings?

A. 

  • For duplicate bookings, AirAsia only allows refund requests to be submitted for the second and subsequent PNR(s). The first PNR must be maintained in the system and is not eligible for a duplicate booking refund.
  • To ensure the correct PNR is selected, I recommend using the booking creation date and time as the identifier when submitting the refund request. This will help avoid rejection by the system or the support team during validation, as requests that do not meet the airline's requirements will not be approved.
  • Example:

PNR01 – Maintain in the system (original booking/main PNR)

PNR02 – Eligible for refund as a duplicate of PNR01

PNR03 – Eligible for refund as a duplicate of PNR01


When processing the refund request, you may use PNR01 as the value of  the duplicatedWith field for duplicate validation, regardless of how many duplicate PNRs were subsequently created.