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.

​

Connection classification

Every connection carries a classification that records who owns and approves its distribution. The control plane sets it. It is never inferred from the provider’s auth model or from where an adapter runs.

• Network connection (network) is a supplier-approved connection on the Voyant Network.
• Native Network connection (native_network) distributes supplier-approved inventory managed in Voyant Run.
• Private external connection (private_external) is a reseller-owned connection to an external supplier, using credentials you hold.

The classification drives the private-connection plan limit, described in Run, Network, and Connect.

​

Run, Network, and Connect

Connect sits inside a three-part model. Keep the three distinct.

• Voyant Run is the managed runtime that executes your connections and meters usage. Run plans set a limit for private connections.
• Voyant Network is the supplier-approved fabric that Network and Native Network connections run on.
• Voyant Connect is the connectivity layer you configure: operators, providers, connections, and credentials.

Network and Native Network connections are supplier-approved and do not count toward your Run plan’s private-connection limit. A Private external connection uses reseller-owned credentials and counts toward that limit.

​

Credential

A credential is the supplier authentication stored on a connection. For Private external connections, the reseller brings and owns those credentials. For Network and Native Network connections, credentials stay with the supplier-owned shared integration and are not exposed to approved resellers.

​

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 platform’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