A common question we receive is, “Why would we need your API if we already have our own?” It’s a great question.
When integrating with a third-party connection hub like Traveltek, Revelex, Odysseus,
or Avoya, there are three key steps to consider:
Step 1: Standards Compliance
The first thing a connection hub does is review your API for quality and adherence to
their standards. Cruise lines that build their own APIs often design them specifically for
their own platforms, which can complicate integration with third-party hubs. For
successful connectivity, the API needs to expose all required endpoints in a
standardized way that aligns with the connection hub’s protocols. Otherwise, the
integration can’t proceed, making it challenging for niche or specialty cruise lines to be
displayed effectively in aggregated search results alongside larger players.
Step 2: Integration Effort and Cost
The time and cost of integration depend on the effort required to adapt the API to the
connection hub’s needs. Even if an API passes the initial quality check, a unique or non-
standard API can incur higher development and maintenance costs due to
customization requirements. Hubs will also assess potential booking volumes and
customer network value to determine whether the connection is worth their resources.
Step 3: Ongoing Support and Resources
During integration, the connection hub will need consistent access to your IT team to
ensure that endpoints are connected correctly, and the end product meets their
standards. If sufficient resources aren’t available, development can be delayed or even
halted. Maintaining a reliable connection is critical, as hubs may disconnect services
that cause booking errors or require excessive support.
How Cabin Select Addresses These Challenges
Cabin Select was designed by experts with 30+ years of combined experience working
with leading connection hubs. Our solution simplifies all three steps:
Step 1
The Cabin Select API can bridge any gaps by consuming your existing
API and standardizing your cruise product for seamless third-party consumption,
while still supporting your internal infrastructure.
Step 2
We are already integrated with top connection hubs like Revelex, Odysseus,
Travtech, Traveltek, Avoya, and others, Cabin Select’s standardized API
minimizes integration time and costs, requiring less maintenance from
connection hubs.
Step 3
The Cabin Select API structure is consistent across cruise lines,
connection hubs experience lower support demands, resulting in greater
reliability and streamlined onboarding.
Using Cabin Select’s API to optimize your existing one ensures smoother,
faster, and more cost-effective third-party integration. Plus, as part of Cabin Select,
you’re joining a collective voice of cruise lines rather than navigating the integration
landscape alone.
