What TransMékong sells, in our own words: services (a hotel night, a cruise, a
transfer), their variants and sale types (a room category, a cabin,
a seat), date-first availability that tells closed from full, a
quote that explains itself, and a hold → confirm booking lifecycle.
Served today for accommodation (Nam Bộ, the Lighthouse); the other families —
overnight cruise, day cruise, transfer, getaway — are designed and answer family-unmodelled
until they are served.
Base URL https://api.transmekong.com/v1
Paths below are relative to the base. Every timestamp is RFC 3339 in Vietnam time (+07:00);
money is integer VND. An error is {error: <token>, message} — branch on the token, never
parse the message.
?serviceFamily=, ?exclusivity=, ?date=closed distinct from full/quote — a priced answer carrying the rules that touched it. Send your key here too: it changes the price, not the accesshold competence, in the Authorization header and nowhere else/bookings — the hold (a cart, minutes long); idempotent on your attemptKey/bookings/{bookingId} — the booking as it stands: the state to poll/bookings/{bookingId}/confirm · /cancel · /extend — the lifecycleA test-competence key rehearses the whole lifecycle against an ephemeral store on this
same address — nothing real moves, every booking answer says testMode: true.
A read key for the open group needs no account; a booking-capable key is issued to trade clients.
Machine-readable summary: /llms.txt. The OpenAPI 3.1 contract
(OFFER_API.yaml) is handed to integrators on request — write to the address below.
Contact: api@transmekong.com · +84 (0)292 382 9540