Skip to main content

Edge Connect

Edge Connect gives Kaptio one connection point to a growing ecosystem of supplier services. Your booking workflow uses one stable contract while Kaptio expands the catalog behind it.

Connect once. Expand without rewiring.

Established connectors and new native adapters appear through the same Kaptio interface, so each addition grows the catalog without changing how your org starts a supplier request.

Explore the catalog →

A catalog built around the booking workflow​

The catalog spans the supplier families used to build and operate an itinerary. Availability for a specific tenant depends on the provider agreement, credentials, markets, and verified capability set.

Accommodation

Catalog

Search live availability and rates, then manage the supported booking lifecycle from Kaptio.

SearchBookRetrieve

Air

Catalog

Connect flight distribution, reservation, import, and retrieval services to the itinerary workflow.

GDSDistributionImport

Multi-day packages

Catalog

Bring packaged tours spanning multiple days into the same supplier catalog, with capabilities verified per provider.

PackagesTouringMulti-day

Activities and transfers

Catalog

Connect the experiences and transport services that complete the trip around its core itinerary.

ActivitiesTransfersExperiences

Rail

Catalog

Keep rail search and booking as a distinct product family with its own distribution contract and lifecycle.

SearchEvaluateBook

See Available connectors for the established connector families and their connection models.

New connectors join the catalog faster​

New native adapters are built within one implementation and test boundary. Supplier protocol handling, mapping, state, fixtures, and contract tests evolve together.

This supports a delivery process designed to move from supplier documentation to a verified adapter in weeks:

  1. Kaptio models the supplier protocol from its documentation and sanitized sample messages.
  2. Fixture-first tests prove mapping and error behaviour without depending on a live supplier system for every development cycle.
  3. Engineering agents can assist with bounded protocol-to-contract tasks, while human review remains mandatory.
  4. Contract replay and supplier test-environment checks protect the Kaptio behaviour before activation.

The result is a repeatable way to add connectors without introducing a different integration shape for every supplier. See Onboarding a supplier for the inputs and verification stages.

Speed and safety services can grow with each connector​

Edge Connect is also a platform for adding reusable performance and reliability services around native adapters. The foundation provides durable state and tenant isolation; each connector can then activate the services that fit its supplier protocol and data.

Session reuse

Foundation

Reuse valid supplier sessions instead of repeating avoidable authentication work.

Duplicate protection

Foundation

Recognize repeated booking submissions and return the stored result safely.

Response caching

Per connector

Add caching where supplier rules, useful hit rates, and acceptable staleness make it safe.

Reconciliation

Per connector

Track supplier-side changes and keep booking state aligned where the supplier supports it.

These capabilities are applied deliberately rather than enabled as one blanket policy. This lets Kaptio increase speed and protection without treating volatile availability like static content. See Performance and reliability.

What the connectivity layer covers​

The common booking contract supports the lifecycle needed for live supplier inventory:

  • search for availability and rates,
  • reserve and book,
  • retrieve the supplier booking,
  • calculate and confirm an amendment,
  • calculate and confirm a cancellation,
  • reconcile changes made in the supplier system.

Not every supplier exposes every step in the same way. An adapter translates the common contract into the supplier's protocol and reports explicitly when a supplier does not support a capability. It does not invent a result that the supplier did not provide.

See Booking lifecycle for the complete flow.

Security and tenant isolation​

Supplier credentials are stored in Kaptio's encrypted secret store and scoped to your tenant. They are not committed to configuration files and are not shared between tenants.

Sessions, booking references, and duplicate-submission records are also tenant-scoped. A request is resolved to a tenant before supplier state is read or written, and one tenant cannot retrieve another tenant's supplier session or booking.

For the platform-wide model, see Security model.

Established connectors continue unchanged​

Edge Connect does not replace or deprecate Kaptio Connect. It provides one entry point for both established and new connections:

  • existing connectors continue to run on Kaptio Connect,
  • Edge Connect passes their requests through without changing the established supplier contract,
  • new native adapters can be activated one tenant at a time,
  • no full-catalog rewrite or simultaneous migration is required.

Your Kaptio org uses the same request contract regardless of which runtime serves the connector. Edge Connect architecture explains the native and pass-through paths.

Where to go next​