Act 1 · Business outcome
One contract, many partner channels
Meridian Travel publishes trips, availability, baskets, pricing, Edge Pay, and bookings through a single Journeys v1 contract. Partners integrate once and render the same commerce objects on their own surfaces.
Commerce thread
Select a trip to carry through channels and the API explorer. Vietnam Discovery is the default.
From contract to channels
The same basket and booking identifiers flow through every channel. Settlement, payouts, and webhooks remain on the network vision roadmap.
Branding from journey.yaml
The hosted experience is themed by the tenant configuration file. Switch a brand preset to
re-theme this page live and see the matching branding block.
Technical capability map
| Capability | Route | Maturity |
|---|
Act 1 · Business outcome
Shared commerce across surfaces
The selected trip and basket identifiers persist as you preview how partners expose Meridian inventory.
Not live in this sample: cross-operator marketplace settlement, automated payouts, outbound webhooks, booking amendments, and cancellations.
Act 2 · Partner integration
Sandbox access request
Request a sandbox bearer API key. Authentication in this sample is API key only. Required fields are validated before a simulated request ID is issued.
Sandbox access uses bearer API keys. Production promotion follows a separate commercial review.
Request submitted.
Status: Pending review. Meridian supplier admin will review in Act 3.
Act 2 · Partner integration
Guided API explorer
Six stages from catalog to booking. Simulates auth, latency, request IDs, and rate limits in the browser.
Base path: /api/journeys/v1.
Choose a room
Select a room option before creating a basket.
The demo key skips the access-request and approval acts so you can start the guided flow immediately. Run Acts 2 and 3 in full to see the governed credential lifecycle.
Error scenarios (optional)
Complete each stage using the primary action above.
Act 3 · Operator governance
Supplier admin review
Review partner requests, grant catalogue access, and issue sandbox bearer keys.
Partners see request status after submission. Supplier staff use Supplier admin to provision access.
Your latest request
No request submitted yet.
Partner access review
No access request to review. Submit a request from Act 2 first.
Request declined.
Sandbox key ready
Your sandbox bearer key has been issued. Open the API explorer to paste it and begin the guided flow.
Sandbox API key management
Masked by default. Rotate or revoke to simulate credential lifecycle.
Rotate this sandbox key? The previous key will stop working immediately.
Revoke this sandbox key? API calls will return 401 until a new key is issued.