Overview
The Legacy Pull Sellers API was our first Sellers API, launched back in 2012. It is now deprecated and should not be further developed. Since then, we have launched a new Pull Sellers API, in which Travelgate currently plays a proactive role in developing API integrations on behalf of the Seller.
How requests flow in this API
The Legacy Pull Sellers API is Buyer-driven. For every method (content, booking flow and booking management), the flow is always the same:
- Initiates the call: the Buyer, through Travelgate.
- Processes and returns the data: the Seller.
- Receives the result: the Buyer.
The Seller's system is reactive: it only receives and answers requests, it never queries Travelgate for data. So if you are a Seller and want to consult the bookings you have received in our platform, this API (and methods such as Reservation List or Reservation Read) is not the way to do it — those calls return bookings to the Buyer who made them, not to the Seller. Use your booking reporting/reservations tooling instead.
The only exception is the Configuration method, which Travelgate initiates to retrieve the Seller's setup template.