What the Public API covers
- Catalog browsing across owned and sourced inventory.
- Departure and product detail pages.
- Pricing preview and sellability resolution.
- Booking-session flows that lead to checkout.
- Customer-facing itinerary reads and self-service.
Base URL
Every request goes to your workspace, under/api:
{workspace} is the first part of your admin address. The paths on this page and in the API reference start at /v1, so add them to https://{workspace}.onvoyant.com/api.
The boundary
The HTTP transport draws a clear line between staff and customer surfaces:/v1/admin/*serves staff and operator surfaces./v1/public/*serves external, customer-facing surfaces.
/v1/public is a union rather than a single module’s namespace. Invitations mount
there from auth; proposals and bookings from trips; and operator profile,
operator settings, payment-link config and travel-credit validation each mount from
their own module. Whatever owns the name does not own every route; route ownership follows the selected deployment graph.
Keys
Some public reads need no key. Anything that depends on a sales channel needs one.
Without what they need, these routes answer
401 or 403.
Create keys in the admin under Settings, then API, on the Public keys tab. Send the key in the x-api-key header. There are two types:
vpk_publishable: for browser code. It works only from the sites listed under Allowed websites on the key, so the request must carry a matchingOriginheader. Browsers add that header themselves. From anywhere else, Voyant ignores the key and treats the request as having no key.vsk_secret: for your own server. It reaches every public route and needs noOriginheader. Never put it in browser code.
Browsers
A browser can call the API only from a site listed under Allowed websites on one of your keys. This applies to product reads too, even though they need no key. Other sites get no CORS headers, so the browser blocks the response.Packages
To build a custom frontend against the public contract, you can install@voyant-travel/storefront-sdk. Its name predates this surface being called the
Public API. It is a final release, so check that it covers the routes you need. See
Consume the API for a working setup and
SDKs overview for which packages still get releases.
@voyant-travel/public-api-contracts carries the customer-portal request and
response shapes, so you can validate /v1/public/customer-portal payloads in a
browser without the server.
The catalog projection that powers discovery is produced by the
catalog module and can be enriched with
Connect sourced inventory.