Expose experience availability and bookings to Viator through a Reservation System API
domain: docs.viator.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Review the Viator Reservation System API technical documentation to understand that your own booking system, not Viator, hosts the API endpoints Viator calls
Implement a real-time availability endpoint that returns current openings and pricing for your bookable products so Viator can display accurate slots
Implement booking creation and cancellation endpoints Viator can call after a customer books through Viator's marketplace
Implement an availability notification endpoint so your system can proactively push changes (e.g. a slot selling out) rather than waiting to be polled
Support Viator's batch pricing calls so multiple date/party-size combinations can be priced in one round trip instead of one call per combination
Coordinate onboarding and credentials with Viator's partner/integration team, since becoming a connected reservation system is a partner enablement process, not an open self-serve signup
Known gotchas
The naming is easy to misread: Viator's 'Reservation System API' is implemented BY the supplier's booking system, while the separate 'Partner API' is what merchants/affiliates call INTO Viator — confirm which direction you're building before writing code
Real-time availability responses are expected to be fast and accurate; stale or slow availability endpoints can get an integration flagged or suspended by Viator
TripAdvisor Experiences listings are powered through this same Viator supplier/partner infrastructure rather than a separate TripAdvisor-branded API
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?