Skip to main content
Voyant Connect is the supplier and inventory integration layer. Its mission is to normalize the travel industry: take inventory from many different suppliers, in many different shapes, and present it through one consistent, Connect-normalized model for products, availability, bookings, cruises, and flights. Connect sits beside Voyant Run and Voyant Network. Connections are classified commercially as Network, Native Network, or Private external — see Connect concepts. Private external connections use credentials you hold. Network and Native Network connections use a supplier-owned shared integration that approved resellers can access without consuming their private-connection allowance.

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.
  • An evergreen sandbox connector with synthetic stays, packages, cruises, and flights, plus a Voyant-owned Network market that auto-approves demo grants.

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

Authentication

Connect APIs authenticate with a Voyant API token as a bearer token against https://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.

Private connectors

Host an org-owned supplier adapter behind the external adapter protocol.

Connect SDK

The client surface and how to call it.