Available connectors
Edge Connect presents established connectors and new native adapters through one stable Kaptio interface. Each verified addition grows the catalog without introducing a new connection pattern in your org.
This page lists the provider families represented in the Kaptio Connect production runtime. Availability for a specific tenant still depends on a commercial agreement with the provider, suitable credentials, supported markets, and implementation verification.
Connector catalog
GP Travel Hub
HubAggregated access to multiple travel supplier services, including multi-day package tours, through one provider API.
Amadeus Enterprise
GDSGlobal flight distribution through the established enterprise API connection.
RightRez
Platform APIAirline reservation access for flight booking import and retrieval.
Rail SPI
SPIA standard rail contract that bridges Kaptio to the configured rail distribution service.
The catalog is growing
New native adapters are in delivery. They will appear here only after contract tests, supplier test-environment verification, and tenant acceptance are complete.
How to read the connection model
“Direct” can be ambiguous in travel distribution. The table therefore separates:
- Kaptio connection: whether Kaptio Connect calls the named provider API or a standardized SPI endpoint.
- Supply model: whether that provider is itself a hub, global distribution system, channel platform, or reservation platform between Kaptio and the underlying supplier.
A direct API connection to a distribution platform is not necessarily a direct commercial connection to an individual hotel, activity operator, airline, or rail operator.
Established Kaptio Connect connectors
| Connector | Product families | Kaptio connection | Supply model |
|---|---|---|---|
| GP Travel Hub | Accommodation, multi-day packages, activities, transfers, car hire, flights | Kaptio Connect calls the GP Travel API | Aggregation hub providing access to multiple suppliers |
| Amadeus Enterprise | Flights | Kaptio Connect calls the Amadeus API | Global distribution system |
| RightRez | Flight booking import and retrieval | Kaptio Connect calls the RightRez API | Airline reservation and booking platform |
| Rail SPI | Rail search, evaluate, reserve, book, retrieve, and cancel | Kaptio Connect calls a standardized rail SPI endpoint | The endpoint bridges to the configured rail distribution service |
Test, mock, demonstration, and tenant-specific variants are intentionally excluded from this list. The table describes connector families, not every environment-specific registration of the same adapter.
Suppliers reached through GP Travel Hub
The GP Travel Hub connection multiplies the catalog: one Kaptio connector reaches the suppliers GP Solutions has integrated into the hub. GP Solutions publishes its integration list in Travel API Integrations (March 2026); the summary below reflects that document.
| Supply category | Examples of integrated suppliers |
|---|---|
| Global distribution systems | Amadeus, Galileo (Travelport), Sabre, Sabre NDC |
| Accommodation consolidators and bedbanks | HotelBeds, Innstant, RateHawk, Stuba, Bonotel, Mr&Mrs Smith, iOL hotels |
| Destination management and touring | Jonview, ATS Pacific (AOT Group), Abbey Tours, Allied-T-Pro, TourMappers, Pacific Destinations, Destination Italia, DiscoverHolidays |
| Flights and consolidation | Travelfusion, UTS |
| Transfers | Intui.travel, Iway, Carnect |
| Channel managers | SiteMinder, HyperGuest, Vertical Booking, OpenGDS, Hotelogix, Primalres |
GP Solutions lists further suppliers whose integrations may require a refresh before use (including Expedia, TBO Holidays, SunHotels, G2 Travel, Viator, and Goway), plus past integration experience with providers such as CarTrawler, AVIS, and AutoEurope.
Two qualifications apply when reading that list:
- Hub integration is not tenant availability. A supplier on GP Solutions' list still requires your commercial agreement with that supplier, credentials, and verification of the agreed booking scenarios through the Kaptio connection.
- Capability follows the hub contract. Kaptio exercises each supplier through GP Travel Hub's normalized API, so the available lifecycle for a given supplier is confirmed during implementation, not assumed from the supplier's own product.
What an SPI path means
An SPI path uses a standard contract between Kaptio Connect and an external endpoint. The endpoint is responsible for translating that contract into the downstream provider's protocol.
This allows a provider-specific bridge to expose capabilities such as rail without adding its proprietary protocol directly to Kaptio Connect. From Kaptio's perspective, the lifecycle remains consistent: search, reserve, book, retrieve, and cancel where supported.
Native Edge Connect adapters
New supplier adapters are built on Edge Connect and are added to this page only after their fixture tests, contract tests, supplier test-environment verification, and tenant acceptance are complete.
Until a native adapter is production-ready, existing supplier traffic continues through the established Kaptio Connect path. A connector is not advertised as available based only on code or a development environment.
Capability varies by connector
The presence of a connector does not mean every common lifecycle operation is available for every provider. For example:
- some providers support search but not a temporary hold,
- some expose booking retrieval but no separate amendment quote,
- some return cancellation policy text rather than a real-time cancellation price,
- some require the tenant to contract with the provider before credentials can be issued.
The implementation scope and acceptance scenarios confirm the exact capability set for your tenant. See Booking lifecycle and Onboarding a supplier.