CODEWITHSUNDEEP
sabre
David McMinn
David McMinn

Reputation: 67

Sabre air search and book flow

Hoping for a bit of guidance / reassurance on air search and book flow in Sabre (SOAP API) which I'm integrating with for a client website project.

My client is planning to take payment separately via a 3rd party payment gateway and also have a 3rd party ticketing robot.

The details I have been given from the ticketing robot company is that we should create the PNR then queue transfer to "International/Domestic Agent Q50" (with their PCC).

I've got access to and have been reading the Sabre Dev Studio, have access to the Sabre SOAP API (I have my client's credentials and PCC) and have followed the "Low Far Search and Book" workflow here (https://developer.sabre.com/docs/read/workflows/Low_Fare_Search_and_Book) exchanging EnhancedAirBookRQ and PassengerDetailsRQ for CreatePassengerNameRecordRQ as advised on that page and inserting payment before, my proposed work flow is:

  1. Create a token with TokenCreateRQ
  2. Use token to perform a search with BargainFinderMaxRQ
  3. Display results to customer, customer picks an itinerary / flight segments
  4. Collect customer details from customer
  5. External payment gateway take payment for amount returned in BarginFinderMaxRQ
  6. Book the desired flight segments using the orchestrated API CreatePassengerNameRecordRQ, including:
    • Adding passenger details and flight segments
    • Specifying that the payment was in cash
    • Performing the queue transfer?

I've got BargainFinderMaxRQ coded up and working.

I'm starting the integration with CreatePassengerNameRecordRQ and have noticed the price returned can be different to the price returned from BargainFinderMaxRQ. Which makes me question the above work flow. I selected it due to the easier integration (I can use tokens rather than manage a session and it's just one API call).

So, my questions:

  1. Is my understanding correct, is this the correct work flow for the project? Given that my client is taking payment via an external payment gateway and want to display the final figure to the customer before they pay.

  2. I'm struggling to understand how the ticketing robot fits into the process. Hoping for a steer on how that affects the PNR call(s). Do I still set the ticket type to "7TAW" and queue place onto their PCC + queue number?

Thank you for any help, greatly appreciated.

Upvotes: 2

Views: 1599

Answers (1)

Giancarlo
Giancarlo

Reputation: 1427

1) Yes, the process is correct, but there are scenarios in which airlines change fares or where the airline does not confirm the availability immediately, so when you price you are actually pricing an IATA fare, which is usually more expensive. For particular scenarios, I recommend you to contact the API support.

2) The "7TAW", which is the ticketing time limit, is meant to have the limit set by the airline until when you can issue the ticket without having the possibility of losing the given price. Some airlines require that to be done on the same day of the booking (which is what you are setting with the 7TAW). Some airlines give you some days and some others can give you just 30 minutes after booking. It is almost impossible for us to respond on how would the robot require this to be provided, so for you to be sure, I would recommend you checking with the owners of that robot and ask them how would they want it, maybe they don't even care.

Upvotes: 2

Related Questions