> ## 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.

# Sandbox connector

> Evergreen synthetic inventory for stays, packages, cruises, and flights — plus a Voyant-owned Network market that auto-approves demo grants.

# Sandbox connector

Voyant ships an evergreen sandbox supplier so clients and Voyant can develop against Connect without real supplier credentials. Inventory is generated deterministically at request time (seeded by connection, market, and query) — it never goes stale.

## Provider keys

| Key                      | Role                                                                                                  |
| ------------------------ | ----------------------------------------------------------------------------------------------------- |
| `voyant-sandbox`         | Multi-vertical synthetic supplier. Orgs create sandbox connections and book against it.               |
| `voyant-sandbox-network` | Same Worker, listed as a Voyant-owned Network market. Access requests auto-approve for sandbox demos. |

Both dispatch to the `voyant-sandbox-connector` script in the Connect Workers-for-Platforms dispatch namespace (`CONNECTOR_WORKERS`). Deploy with `pnpm run deploy:dispatch` from [voyant-sandbox-connector](https://github.com/voyant-travel/voyant-sandbox-connector).

## Vertical coverage

* **Stays:** search, quote, lock, confirm, cancel, get
* **Packages:** search, quote, lock, confirm, cancel, get
* **Cruises:** search, quote, lock, confirm, cancel, get
* **Flights:** search, price, book, get, cancel (seatmap/ancillaries later)
* **Shared:** `health`, `validateCredentials`, `syncCatalog` (generated page)

Markets: `RO`, `GB`, `US` (locale-ish labels and currencies). Environment is forced to `sandbox` in connector context.

## Create a sandbox connection

1. Open **Connect → Catalog → Supplier feeds** and select **Voyant Sandbox** (provider key `voyant-sandbox`). It is listed for every org, with no provider grant required.
2. Create a registration with optional blank credentials / demo API key.
3. Search → lock → confirm on stays, packages, cruises, or flights like any other hosted connector.
4. Booking state is ephemeral in the Worker isolate (acceptable for sandbox).

## Connect to Voyant Sandbox Network

For Network grant and commercial-pricing tests:

1. Staff/ops runs `ensureSandboxNetworkMarket` (control plane) against the Voyant-owned org. That creates operator slug `voyant-sandbox-network` with `metadata.sandboxNetworkAutoApprove: true` and a `native_network` connection.
2. A reseller requests access via the Network access-request API.
3. The control plane **auto-approves** with FIT terms and default sandbox markets.

This auto-approve path is **sandbox-only**. It never applies to real Network suppliers — only operators explicitly flagged with `sandboxNetworkAutoApprove`.

## Private-connector / externalAdapter twin

The same Worker RPC paths accept HMAC-signed requests for private-connector probe and client self-hosted adapter demos. Point a private connector's `metadata.externalAdapter.baseUrl` at the public sandbox Worker URL (`https://voyant-sandbox-connector.pixelmakers.workers.dev`) and configure `SIGNING_SECRET` on the Worker to match the provider signing secret.

See [Private connectors](/docs/connect/private-connectors) for the HMAC canonical string and headers.

## Out of scope

* Replacing real TUI / HiSky / Viking feeds
* Full HiSky parity (seatmaps, ancillaries, exchanges) in v1
* Stripe/payout settlement against sandbox bookings
* Production Network listing of synthetic inventory as a real supplier brand