What Connect gives you
- A normalized data plane for products, availability, suppliers, bookings, cruises, and flights, so your code does not care which upstream supplier a result came from.
- A control plane for operators, connections, credentials, provider registrations, grants, links, webhooks, and audit logs.
- Cross-connection reads that aggregate inventory across every connection in an operator’s catalog.
- Provider integration primitives for building new supplier connectors.
The package family
Connect ships four public packages. Which one you use depends on what you are building.connect-sdk
The raw typed HTTP client for the Connect API. Use it from non-Voyant apps and low-level tools.
connect-adapter
Adapts Connect inventory into the framework catalog as a SourceAdapter. Use it inside a Voyant app.
connect-provider-sdk
Primitives for building a provider integration: descriptors and credential helpers.
connect-cruises
Adapts Connect-normalized cruise inventory into a Voyant deployment’s cruises adapter.
Which package do I use?
| You are building | Use |
|---|---|
| A Voyant operator app that should sell Connect inventory | @voyant-travel/connect-adapter |
| A non-Voyant app or tool calling Connect directly | @voyant-travel/connect-sdk |
| A new supplier connector | @voyant-travel/connect-provider-sdk |
| A Voyant deployment selling Connect cruises | @voyant-travel/connect-cruises |
Authentication
Connect APIs authenticate with a Voyant API token as a bearer token againsthttps://api.voyant.travel. For machine-to-machine flows you can exchange OAuth client credentials for a short-lived bearer token. See Connect concepts for the auth and tenancy model, and Authentication for tokens and scopes.
Next steps
Connect concepts
Operators, connections, credentials, grants, and supply models.
Connect SDK
The client surface and how to call it.