Skip to main content

Service documentation

API overview for discovery, booking support, and customer account flows

This page is the human-readable companion to the API catalog advertised from the homepage via HTTP Link headers. It highlights the main web-facing routes agents and integrations are most likely to need.

Discovery

Public discovery endpoints

These routes help agents and integrations understand the public site structure and trip inventory without requiring authentication.

GET/api/search

Search trips, destinations, categories, and guide content.

GET/api/nav-catalog

Read structured navigation and site discovery data.

GET/api/trip-suggestions

Return curated trip suggestions for recommendations and cards.

GET/api/site-settings

Read selected public-facing site settings.

Leads and payments

Inquiry, planner, and booking support

These public routes support the website booking funnel, planner flows, and payment initiation. Validation and rate limiting still apply.

POST/api/leads

Create contact, custom-trip, inquiry, and booking-request submissions.

POST/api/payments

Initiate payment-related flows used by the website checkout experience.

Customer account

Authenticated customer surfaces

Customer routes support sign-in, account retrieval, documents, payments, and personalized recommendations. Protected routes require a customer bearer token.

POST/api/customer/login

Start a customer sign-in flow.

POST/api/customer/register

Register a new customer account.

GET/api/customer/me

Return the authenticated customer profile used by the account dashboard.

Status

Operational health

The API catalog also advertises a lightweight status endpoint so agents and integrations can confirm the web API is reachable before relying on other routes.

GET/api/status

Return a lightweight API health payload.