Quickstart
This integration model is designed for Sellers or suppliers that already expose a real-time pull API. In this scenario, the Seller provides its technical specifications, and Travelgate is responsible for building the connector that connects that API to our network.
This is the standard model when the Seller already has a working pull-based API and Travelgate develops the connectivity layer for the marketplace. Once the connector is implemented, Buyers connected to Travelgate can access the Seller's product without needing to integrate directly with the supplier's system.
What this integration is
A Connector Pull Sellers API allows a supplier to make its inventory and pricing available to the Travelgate marketplace through a real-time API response model.
In practice, the Seller exposes the API endpoints, payloads, and rules needed to retrieve availability, rates, and booking information. Travelgate then creates and maintains the connector that translates that supplier integration into a standard marketplace flow.
This model is especially useful when the Seller already has a functional API and wants to expose its product to multiple Buyers through a single integration point.
How it works
The flow is straightforward:
- The Seller provides the API documentation and technical specifications.
- Travelgate analyzes the contract and defines the integration approach.
- Travelgate builds the connector that adapts the Seller's API to our network and marketplace standards.
- Buyers can access the product through the Travelgate ecosystem without managing a separate direct integration with the Seller.
This means the Seller does not need to build a different integration for each Buyer. Instead, one connector is developed and shared across the network.
Why this is valuable
This model is ideal for suppliers that want to:
- expose real-time availability and pricing
- support dynamic product distribution across multiple Buyers
- reduce the complexity of managing multiple bilateral integrations
- rely on Travelgate to handle the technical connectivity layer
The connector becomes the bridge between the seller's systems and the marketplace, while preserving a consistent buyer experience.
Typical use cases
This approach is commonly used when the Seller already has a mature API and wants to distribute inventory through a Travelgate-powered network. Typical examples include:
- real-time availability retrieval
- dynamic pricing and rate access
- live booking flows managed through Seller endpoints
- marketplace distribution without direct one-to-one implementation by each Buyer
Key benefit for the marketplace
By building a connector once, Travelgate can expose one Seller product to many Buyers in a standardized and scalable way. This reduces operational overhead and improves onboarding speed for both Sellers and Buyers.
If your system already has a pull-based API, this is usually the fastest and most scalable path to marketplace connectivity.