> ## Documentation Index
> Fetch the complete documentation index at: https://voyant.travel/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Voyant Connect

> Supplier and inventory connectivity for travel: normalize catalog once, then distribute it through Network, Native Network, or private external connections.

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](/docs/connect/concepts#connection-classification). 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](/docs/connect/sandbox)** 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.

<CardGroup cols={2}>
  <Card title="connect-sdk" icon="code" href="/docs/connect/connect-sdk">
    The raw typed HTTP client for the Connect API. Use it from non-Voyant apps and low-level tools.
  </Card>

  <Card title="connect-adapter" icon="puzzle-piece" href="/docs/connect/connect-adapter">
    Adapts Connect inventory into the platform catalog as a SourceAdapter. Use it inside a Voyant app.
  </Card>

  <Card title="connect-provider-sdk" icon="screwdriver-wrench" href="/docs/connect/provider-sdk">
    Primitives for building a provider integration: descriptors and credential helpers.
  </Card>

  <Card title="connect-cruises" icon="ship" href="/docs/connect/connect-cruises">
    Adapts Connect-normalized cruise inventory into a Voyant deployment's cruises adapter.
  </Card>
</CardGroup>

## 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 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](/docs/connect/concepts) for the auth and tenancy model, and [Authentication](/docs/sdks/authentication) for tokens and scopes.

## Next steps

<CardGroup cols={2}>
  <Card title="Connect concepts" icon="sitemap" href="/docs/connect/concepts">
    Operators, connections, credentials, grants, and supply models.
  </Card>

  <Card title="Private connectors" icon="plug" href="/docs/connect/private-connectors">
    Host an org-owned supplier adapter behind the external adapter protocol.
  </Card>

  <Card title="Connect SDK" icon="code" href="/docs/connect/connect-sdk">
    The client surface and how to call it.
  </Card>
</CardGroup>