Connect concepts

Connect has a small set of concepts that show up across every package. Understanding them makes the SDK surface easy to navigate.

​

Operator

An operator is the tenant in Connect: the organization whose catalog, connections, and bookings you are working with. Most SDK calls are scoped to an operator, either through the client-level operatorId or a per-call override. In Voyant, one first-party operator maps to one organization.

​

Connection

A connection is a configured link to one supplier under an operator. It carries the supplier’s identity, the provider it uses, its credentials, and its sync and health state. Inventory is read on a connection, and bookings are made against a connection. An operator can have many connections.

​

Credential

A credential is the supplier authentication you bring. Connect’s model is bring-your-own-credentials: you supply the keys or login for each supplier, and Connect uses them to talk to that supplier on your behalf. Credentials belong to a connection.

​

Provider

A provider is a supplier integration type, identified by a provider key such as tui or ventrata. Providers describe what a supplier supports: its categories, its auth model, and the credential form it needs. Connectors register as providers, and connections pick a provider by key.

​

Grant

A grant shares access between operators. Because Connect ingests catalog once and shares it to many, grants are how one operator’s sourced inventory or capability is made available to another. Grants can be issued, updated, revoked, and inspected.

​

Gateway

The gateway is the data plane: the Connect-normalized API surface for products, availability, suppliers, bookings, cruises, and flights. Whatever the upstream supplier looks like, the gateway returns one consistent shape, with provenance fields recording where each record came from.

​

Catalog and projections

Connect builds a normalized catalog from each supplier’s inventory and exposes search documents and projections over it. When a Voyant app consumes Connect through the adapter, these projections flow into the framework’s catalog plane with stable provenance such as source_kind, source_provider, source_connection_id, and source_ref, so a booking can always route back to the connection that produced the projection.

​

Supply models

Inventory falls into two supply models, which determine how it is sold:

• Scheduled inventory has fixed departures or sailings with defined capacity, such as a cruise sailing or a group departure.
• Dynamic inventory is searched and priced live at request time, such as a flight search or a live stays availability lookup.

The catalog surface forks on supply model because the booking mechanic differs. Scheduled inventory locks a known unit; dynamic inventory resolves a fresh offer and then commits it.

​

Provenance and freshness

Connect-normalized reads carry provenance and freshness so consumers know where data came from and how current it is. Per-connection cruise reads, for example, include sourceRef, projection, projectionSchemaVersion, lastSourcedAt, market, and currency when available. This lets you mix sourced inventory into your catalog while still being able to refresh or re-route any individual record.

​

Next steps