Viator API Documentation & Specification - Merchant Partners
Community OpenAPI document · agent-readyDeveloper ToolsSource ControlapiKey28 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically /available/products, /booking/availability. Covers 28 operations with apiKey authentication.
Use for: I need to /available/products, I want to /booking/availability, Search for /booking/availability/dates, Find all /booking/availability/tourgrades
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
<style type='text/css'> code { white-space: nowrap; } a { font-weight: bold; } figure { width: 100%; text-align: center; font-style: italic; font-size: smaller; text-indent: 0; border: thin silver solid; margin: 0.5em; padding: 0.5em; } </style> Updates Latest update: | Date | Description | |------|-------------| | 3 Feb 2021 | Added [Special offers and on-sale pricing](#section/Key-co. The API exposes 28 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the Viator API Documentation & Specification - Merchant Partners to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Viator API Documentation & Specification - Merchant Partners, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fviator.com%2Fviator" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fviator.com%2Fviator" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Viator API Documentation & Specification - Merchant Partners API.
/available/products
/booking/availability
/booking/book
/booking/calculateprice
Monitor Viator API Documentation & Specification - Merchant Partners operational status and events
Use Cases
Patterns agents use Viator API Documentation & Specification - Merchant Partners API for, with concrete tasks.
★ Developer Tools Operations
Use the Viator API Documentation & Specification - Merchant Partners to perform developer tools operations programmatically. The API provides 28 endpoints covering core functionality including /available/products, /booking/availability, /booking/availability/dates.
Call POST /available/products to /available/products
Automated General services Management
Automate general services operations by combining multiple Viator API Documentation & Specification - Merchant Partners endpoints. Agents can /booking/availability and then /booking/availability/dates in a single workflow.
Call POST /booking/availability to /booking/availability, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Viator API Documentation & Specification - Merchant Partners endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.
Search Jentic for '/available/products', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
28 endpoints — <style type='text/css'> code { white-space: nowrap; } a { font-weight: bold; } figure { width: 100%; text-align: center; font-style: italic; font-size: smaller; text-indent: 0; border: thin silver solid; margin: 0.
METHOD
PATH
DESCRIPTION
POST
/available/products
/available/products
POST
/booking/availability
/booking/availability
GET
/booking/availability/dates
/booking/availability/dates
POST
/booking/availability/tourgrades
/booking/availability/tourgrades
POST
/booking/availability/tourgrades/pricingmatrix
/booking/availability/tourgrades/pricingmatrix
POST
/booking/book
/booking/book
POST
/booking/calculateprice
/booking/calculateprice
GET
/booking/hotels
/booking/hotels
POST
/available/products
/available/products
POST
/booking/availability
/booking/availability
GET
/booking/availability/dates
/booking/availability/dates
POST
/booking/availability/tourgrades
/booking/availability/tourgrades
POST
/booking/availability/tourgrades/pricingmatrix
/booking/availability/tourgrades/pricingmatrix
POST
/booking/book
/booking/book
POST
/booking/calculateprice
/booking/calculateprice
GET
/booking/hotels
/booking/hotels
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Viator merchant API by hand means passing its exp-api-key header, picking the production or sandbox host, and stitching the availability, pricing, and booking calls together yourself. Through Jentic you install once, import the Viator API from the API Directory, store the key once, and your agent calls it.
Permission scoping
Viator takes booking and availability targets in the request body rather than the URL path, so scope the agent to the operations it needs, such as checking availability or calculating a price. You choose that set, so a committing operation like booking a tour is not included unless you add it.
Credential isolation
Your Viator API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'check tour availability for a date' or 'calculate a booking price', and Jentic returns the matching Viator operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
FAQs
Specific to using Viator API Documentation & Specification - Merchant Partners API through Jentic.
What authentication does the Viator API Documentation & Specification - Merchant Partners use?
The Viator API Documentation & Specification - Merchant Partners uses an API key passed in the `exp-api-key` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I /available/products with the Viator API Documentation & Specification - Merchant Partners?
Yes. Use the POST /available/products endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Viator API Documentation & Specification - Merchant Partners?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I /available/products through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for '/available/products'. Jentic returns the matching Viator API Documentation & Specification - Merchant Partners operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Viator API Documentation & Specification - Merchant Partners have?
The Viator API Documentation & Specification - Merchant Partners exposes 28 endpoints covering general services, taxonomy services, product services operations.
Can I limit what my agent is allowed to do with the Viator API?
Yes. Jentic One is self-hosted, so your own rules decide which of the Viator operations and credentials the agent can use. Because Viator takes booking and availability targets in the request body rather than the URL path, you scope the agent to the operations it needs, such as checking availability or calculating a price. A committing operation like booking a tour is not included unless you add it.
GET STARTED