Skip to main content

Distribution API sample

The Meridian Travel distribution sample demonstrates how one Edge Journeys integration can support multiple sales channels without creating a second booking stack.

Open the interactive Meridian Travel sample

The sample is self-contained and uses fictional data. It does not make network requests, issue real credentials, create customer records, or transact against a live tenant.

What the sample demonstrates​

The walkthrough is organised into three acts:

  1. Business outcome — one Journeys contract supports partner APIs, white-label booking, trade, chat, and future network distribution.
  2. Partner integration — a partner requests a sandbox bearer key and follows a guided six-stage flow from catalog search to booking.
  3. Operator governance — a simulated supplier administrator reviews requested access, controls product and scope grants, and manages the credential lifecycle.

The API explorer follows the published Journeys contract:

GET  /catalog/trips
GET  /catalog/rooms
POST /baskets
GET  /baskets/{basketId}/prices
POST /baskets/{basketId}/bookings

The selected trip and commerce state then appear in five example channels:

  • a partner distribution API;
  • a Meridian-branded booking journey;
  • a travel-agent portal with commission visibility;
  • conversational trip discovery through Journeys chat;
  • a future Kaptio distribution-network listing.

Only the client experience changes. Catalog, basket, pricing, payment, and booking objects remain on the shared Journeys contract.

Shortcuts and branding​

Two conveniences make the sample easy to explore in any order:

  • Demo sandbox key. The API explorer offers a predefined demo key so you can start the guided six-stage flow immediately, without first completing the access-request and approval acts. Run Acts 2 and 3 in full when you want to show the governed credential lifecycle.
  • Brand presets. The overview includes a journey.yaml branding block with selectable presets. Switching a preset re-themes the page live — header color, primary actions, and heading typography — mirroring how the real branding configuration themes a hosted journey without code deploys.

Capability boundaries​

The sample labels every capability by maturity:

LabelMeaning
AvailableThe underlying route or capability is present in the published Journeys contract.
SimulatedThe sample provides an illustrative enablement interface, such as partner review and API-key lifecycle.
VisionThe interface represents a future distribution-network capability rather than a live service.

The cross-operator marketplace, automated payouts, outbound commerce webhooks, amendments, and cancellations are not presented as live capabilities.

Suggested demonstration​

Use Presenter mode for a repeatable eight-cue walkthrough:

  1. Establish the business outcome and compare the channel surfaces.
  2. Submit a sandbox-access request using the API-key authentication model.
  3. Review requested products, markets, scopes, and rate limits before approval.
  4. Hand the issued key explicitly into the API explorer.
  5. Progress through Trips, Rooms, Basket, Pricing, Payment, and Booking.
  6. Close on governed key rotation/revocation and the distinction between available, simulated, and vision capabilities.

For the full endpoint definitions, see the Journeys API reference and OpenAPI specification.