Viator

Viator is a Tripadvisor company and the largest online marketplace for tours, activities and travel experiences, headquartered in the United States and listing more than 300,000 bookable products across roughly 2,500 destinations. It sits on the demand side of the travel distribution chain as an aggregator and reseller of third-party operator inventory, and on the supply side as the channel counterparty that tour operators' reservation systems connect into. Its API posture is unusually open for travel: the full Viator Partner API v2 OpenAPI, the legacy v1 affiliate and merchant specifications, the Viator Reservation System (supplier) API and four Postman collections are all published without a login at docs.viator.com, and Basic Access affiliate keys are issued self-serve at no cost on account creation. Everything beyond that is gated - Full Access, Full Access plus Booking, Merchant and supplier connectivity all require qualification by Viator and, for transactional integrations, passing a two-part front-end and back-end certification. No open travel standard is referenced anywhere in the specifications: the contract is entirely Viator-proprietary, product identifiers are Viator-internal, and partners are contractually required to prevent search engines indexing Viator reviews and unique content.

Viator publishes 17 API contracts indexed on the APIs.io network, including Attraction services API, Attractions API, Auxiliary API, and 14 more. Tagged areas include Travel, United States, Tours and Activities, Experience, and OTA.

The Viator catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

Viator’s developer surface includes authentication, documentation, developer portal, support, engineering blog, API reference, getting-started guide, and 36 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

49.7/100 developing ▬ flat Agent 48/100 agent native saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

4 published contracts 5 Agent Skills

Travel United States Tours and Activities Experience OTA Booking Distribution Marketplace Affiliates Hospitality

What this lets a business do 4

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Consumer Travel, Events & Local Services

AE-210

Attraction servicesAttractionsAvailabilityProduct services

GET /attraction GET /attraction/products POST /search/products GET /product

Reservation & Booking Management

BC-4020

Booking servicesBookingsReservation system APIs

POST /booking/book POST /booking/status GET /booking/voucher POST /bookings/hold

Travel Product & Inventory Management

BC-4000

ProductsTaxonomy services

GET /taxonomy/destinations GET /taxonomy/categories POST /taxonomy/attractions GET /products/modified-since

Consumer Commerce

AE-140

Payments

POST /v1/checkoutsessions/{sessionToken}/paymentaccounts

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 49.7/100 · developing

Contract Quality 10.6 / 19

Developer Ergonomics 9.4 / 15

Access Clarity 6.7 / 15

Operational Transparency 3.1 / 10

Contract Governance 1.6 / 9

Discoverability 5.4 / 8

Regulatory Posture 3.7 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 48/100 · agent native

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 4 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 0 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/viator/"><img src="https://apis.io/badge/viator/card.svg" alt="Viator on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
Pagination +5 pts — share of collection GETs (an array, or one wrapped in data/items/results ...) that declare a page/limit/offset/cursor parameter, a Link header or a next/cursor field; na with no collection GETs
Protected Resource Metadata +5 pts — a served /.well-known/oauth-protected-resource carrying `resource` (documented), and naming its authorization_servers (verified)

3 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 44.7 — up to +11.1 composite points
Contract Quality scores 56.4 — up to +10.9 composite points
Contract Governance scores 18.2 — up to +9.8 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/viator/apis.yml: open an issue on github.com/api-evangelist/viator to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Travel and Airline Distribution	standard	17.2 (thin)	-	-
APIs.guru OpenAPI Directory (API definition directory)	standard	17.2 (thin)	-	-
OCTO Tours, Activities & Attractions Connectivity (members, known implementations, self-certification)	standard	17.2 (thin)	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 17

Individual APIs this provider publishes, each with its own machine-readable definition.

Viator Attraction services API

Attraction services

Viator Attractions API

The Attractions API from Viator — 2 operation(s) for attractions.

Viator Auxiliary API

The Auxiliary API from Viator — 6 operation(s) for auxiliary.

Viator Availability API

The Availability API from Viator — 4 operation(s) for availability.

Viator Booking services API

Booking services

Viator Bookings API

The Bookings API from Viator — 13 operation(s) for bookings.

Viator Deprecated API

This section lists endpoints that are no longer recommended for new or updated integrations. These endpoints remain available for existing connections only, will stop receiving ...

Viator Deprecated services API

Deprecated services

Viator General services API

General services

Viator Payments API

The Payments API from Viator — 1 operation(s) for payments.

Viator Product services API

Product services

Viator Products API

The Products API from Viator — 7 operation(s) for products.

Viator Reservation system APIs API

This section describes all the possible services, some of which are mandatory, that reservation systems can develop to integrate with Viator. All API requests made by Viator to ...

Viator Support services API

Support services

Viator Taxonomy services API

Taxonomy services

Viator Utility services API

Utility services

Viator APIs

This section describes the Viator built API(s) available for reservation system consumption. **Note**: For these APIs, the request is sent **to** Viator and the response is rece...

Scroll for all 17

Open Collections 4

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Viator API Documentation & Specification - Affiliate Partners

OPEN COLLECTION

Viator API Documentation & Specification – Merchant Partners

OPEN COLLECTION

Viator Partner API

OPEN COLLECTION

Viator Reservation System API

OPEN COLLECTION

Agent Skills 5

Packaged agent skills for driving this provider's APIs from an AI assistant.

Amend, cancel and reconcile Viator bookings

AGENT SKILL

Book a multi-item Viator cart and tokenise payment

AGENT SKILL

Ingest and maintain the Viator product catalogue

AGENT SKILL

Implement Viator reservation-system connectivity (supplier side)

AGENT SKILL

Search, check availability and complete a Viator booking

AGENT SKILL

Rate Limits 1

Documented rate limits and quota policies.

Viator Rate Limits

0 limits

RATE LIMITS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Viator Events

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Viator API Rules

62 rules · 45 errors 10 warnings 7 info

SPECTRAL

OpenAPI Overlays 4

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Viator Affiliate Api V1 Overlay

2 actions · update · viator-affiliate-api-v1-openapi.json

DERIVED

Viator Merchant Api V1 Overlay

3 actions · update · viator-merchant-api-v1-openapi.json

DERIVED

Viator Partner Api V2 Overlay

10 actions · update · viator-partner-api-v2-openapi.json

DERIVED

Viator Reservation System Api Overlay

10 actions · update · viator-reservation-system-api-openapi.json

DERIVED

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Viator Authentication

apiKey · 3 schemes

SECURITY

Viator Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Viator Agentic Access

86 operations · 48 acting

AGENTIC

Resources

Get Started 6

Portal, sign-up, and the first successful call

Portal

DeveloperPortal

GettingStarted

SignUp

Login

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

X-MCPServerCandidate

X-MCPServerCandidate

AgentSkill

AgentSkill

LLMsTxt

LLMsTxt

Design & Contract 8

Pagination, idempotency, versioning, errors, and events

Conventions

Idempotency

ErrorCatalog

Lifecycle

Conformance

DataModel

Components

Webhooks

Scroll for all 8

Build 6

SDKs, sample code, and the tooling you integrate with

PostmanCollection

PostmanCollection

PostmanCollection

PostmanCollection

PostmanCollection

PostmanCollection

PostmanCollection

PostmanCollection

Packages

Packages

ToolCrosswalk

ToolCrosswalk

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 4

Status, limits, changes, and where to get help

Support

RateLimits

Deprecation

ChangeLog

Commercial 3

Pricing, plans, and the legal terms of use

Pricing

Pricing

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

Website

Website

Blog

Blog

LinkedIn

Other 5

Properties that don't map to a standard resource type

CapabilityMap

Overlay

Overlay

Overlay

Overlay

Source (apis.yml)

aid: viator
url: https://raw.githubusercontent.com/api-evangelist/viator/refs/heads/main/apis.yml
name: Viator
kind: company
description: 'Viator is a Tripadvisor company and the largest online marketplace for tours, activities and travel experiences,
  headquartered in the United States and listing more than 300,000 bookable products across roughly 2,500 destinations. It
  sits on the demand side of the travel distribution chain as an aggregator and reseller of third-party operator inventory,
  and on the supply side as the channel counterparty that tour operators'' reservation systems connect into. Its API posture
  is unusually open for travel: the full Viator Partner API v2 OpenAPI, the legacy v1 affiliate and merchant specifications,
  the Viator Reservation System (supplier) API and four Postman collections are all published without a login at docs.viator.com,
  and Basic Access affiliate keys are issued self-serve at no cost on account creation. Everything beyond that is gated -
  Full Access, Full Access plus Booking, Merchant and supplier connectivity all require qualification by Viator and, for transactional
  integrations, passing a two-part front-end and back-end certification. No open travel standard is referenced anywhere in
  the specifications: the contract is entirely Viator-proprietary, product identifiers are Viator-internal, and partners are
  contractually required to prevent search engines indexing Viator reviews and unique content.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - rate-limits
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://partnerresources.viator.com/wp-content/uploads/2023/08/V-logo_Green.png
tags:
- Travel
- United States
- Tours and Activities
- Experience
- OTA
- Booking
- Distribution
- Marketplace
- Affiliates
- Hospitality
tags_raw:
- Travel
- United States
- Tours and Activities
- Experiences
- OTA
- Booking
- Distribution
- Marketplace
- Affiliate
- Hospitality
created: '2026-07-28'
modified: '2026-09-16'
specificationVersion: '0.23'
apis:
- aid: viator:viator-attraction-services-api
  name: Viator Attraction services API
  description: Attraction services
  humanURL: https://docs.viator.com/partner-api/technical/
  baseURL: https://api.viator.com/partner
  tags:
  - Attraction services
  properties:
  - type: OpenAPI
    url: openapi/viator-attraction-services-api-openapi.yml
  - type: Documentation
    url: https://docs.viator.com/partner-api/technical/
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Products
  - type: PostmanCollection
    url: collections/Viator-Merchant-API-v2.postman_collection.json
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Availability
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Bookings
  - type: PostmanCollection
    url: collections/Viator-Affiliate-Booking-API-v2.postman_collection.json
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Payments
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Attractions
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Auxiliary
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/api-overview/
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/connectivity-overview/index.html
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/sapi-manual-latest/
  - type: Documentation
    url: https://docs.viator.com/partner-api/merchant/technical/
  - type: Documentation
    url: https://docs.viator.com/partner-api/affiliate/technical/
- aid: viator:viator-attractions-api
  name: Viator Attractions API
  description: The Attractions API from Viator — 2 operation(s) for attractions.
  humanURL: https://docs.viator.com/partner-api/technical/
  baseURL: https://api.viator.com/partner
  tags:
  - Attractions
  properties:
  - type: OpenAPI
    url: openapi/viator-attractions-api-openapi.yml
  - type: Documentation
    url: https://docs.viator.com/partner-api/technical/
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Products
  - type: PostmanCollection
    url: collections/Viator-Merchant-API-v2.postman_collection.json
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Availability
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Bookings
  - type: PostmanCollection
    url: collections/Viator-Affiliate-Booking-API-v2.postman_collection.json
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Payments
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Attractions
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Auxiliary
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/api-overview/
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/connectivity-overview/index.html
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/sapi-manual-latest/
  - type: Documentation
    url: https://docs.viator.com/partner-api/merchant/technical/
  - type: Documentation
    url: https://docs.viator.com/partner-api/affiliate/technical/
- aid: viator:viator-auxiliary-api
  name: Viator Auxiliary API
  description: The Auxiliary API from Viator — 6 operation(s) for auxiliary.
  humanURL: https://docs.viator.com/partner-api/technical/
  baseURL: https://api.viator.com/partner
  tags:
  - Auxiliary
  properties:
  - type: OpenAPI
    url: openapi/viator-auxiliary-api-openapi.yml
  - type: Documentation
    url: https://docs.viator.com/partner-api/technical/
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Products
  - type: PostmanCollection
    url: collections/Viator-Merchant-API-v2.postman_collection.json
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Availability
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Bookings
  - type: PostmanCollection
    url: collections/Viator-Affiliate-Booking-API-v2.postman_collection.json
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Payments
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Attractions
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Auxiliary
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/api-overview/
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/connectivity-overview/index.html
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/sapi-manual-latest/
  - type: Documentation
    url: https://docs.viator.com/partner-api/merchant/technical/
  - type: Documentation
    url: https://docs.viator.com/partner-api/affiliate/technical/
- aid: viator:viator-availability-api
  name: Viator Availability API
  description: The Availability API from Viator — 4 operation(s) for availability.
  humanURL: https://docs.viator.com/partner-api/technical/
  baseURL: https://api.viator.com/partner
  tags:
  - Availability
  properties:
  - type: OpenAPI
    url: openapi/viator-availability-api-openapi.yml
  - type: Documentation
    url: https://docs.viator.com/partner-api/technical/
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Products
  - type: PostmanCollection
    url: collections/Viator-Merchant-API-v2.postman_collection.json
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Availability
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Bookings
  - type: PostmanCollection
    url: collections/Viator-Affiliate-Booking-API-v2.postman_collection.json
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Payments
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Attractions
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Auxiliary
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/api-overview/
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/connectivity-overview/index.html
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/sapi-manual-latest/
  - type: Documentation
    url: https://docs.viator.com/partner-api/merchant/technical/
  - type: Documentation
    url: https://docs.viator.com/partner-api/affiliate/technical/
- aid: viator:viator-booking-services-api
  name: Viator Booking services API
  description: Booking services
  humanURL: https://docs.viator.com/partner-api/technical/
  baseURL: https://api.viator.com/partner
  tags:
  - Booking services
  properties:
  - type: OpenAPI
    url: openapi/viator-booking-services-api-openapi.yml
  - type: Documentation
    url: https://docs.viator.com/partner-api/technical/
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Products
  - type: PostmanCollection
    url: collections/Viator-Merchant-API-v2.postman_collection.json
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Availability
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Bookings
  - type: PostmanCollection
    url: collections/Viator-Affiliate-Booking-API-v2.postman_collection.json
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Payments
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Attractions
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Auxiliary
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/api-overview/
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/connectivity-overview/index.html
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/sapi-manual-latest/
  - type: Documentation
    url: https://docs.viator.com/partner-api/merchant/technical/
  - type: Documentation
    url: https://docs.viator.com/partner-api/affiliate/technical/
- aid: viator:viator-bookings-api
  name: Viator Bookings API
  description: The Bookings API from Viator — 13 operation(s) for bookings.
  humanURL: https://docs.viator.com/partner-api/technical/
  baseURL: https://api.viator.com/partner
  tags:
  - Booking
  tags_raw:
  - Bookings
  properties:
  - type: OpenAPI
    url: openapi/viator-bookings-api-openapi.yml
  - type: Documentation
    url: https://docs.viator.com/partner-api/technical/
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Products
  - type: PostmanCollection
    url: collections/Viator-Merchant-API-v2.postman_collection.json
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Availability
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Bookings
  - type: PostmanCollection
    url: collections/Viator-Affiliate-Booking-API-v2.postman_collection.json
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Payments
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Attractions
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Auxiliary
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/api-overview/
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/connectivity-overview/index.html
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/sapi-manual-latest/
  - type: Documentation
    url: https://docs.viator.com/partner-api/merchant/technical/
  - type: Documentation
    url: https://docs.viator.com/partner-api/affiliate/technical/
- aid: viator:viator-deprecated-api
  name: Viator Deprecated API
  description: 'This section lists endpoints that are no longer recommended for new or updated integrations. These endpoints
    remain available for existing connections only, will stop receiving new features or behavior improvements, and will eventually
    be retired once an end-of-life procedure is agreed with Viator (see the [v2 migration guide](#tag/v2-migration-guide)
    for details).


    For all new development, use the current, fully supported endpoints documented in the main sections of this guide.


    ### REST v1.0 endpoints — deprecated


    - [Real-time Availability API](#operation/availability) — superseded by the Availability Check API and Reserve API

    - [Batch Availability API](#operation/batchAvailability) — superseded by the Calendar API

    - [Batch Pricing API](#operation/batchPricing) — superseded by the Calendar API

    - [Availability Notifications (2) API](#operation/availabilityNotification2) — superseded by the Event Notifications API


    ### Data format: XML — deprecated


    XML (`application/xml`) requests and responses are deprecated. **New integrations must use JSON (`application/json`) exclusively.**
    XML remains available for existing v1.0 integrations only and will receive no new features or behavior improvements. All
    v2.0 endpoints are JSON-only. XML will eventually be retired once an end-of-life procedure is agreed with Viator.


    ### SOAP interface (WSDL/XSD) — deprecated


    The legacy SOAP interface definitions are deprecated. SOAP is no longer supported for new or updated integrations; use
    the REST endpoints documented in the main sections of this guide instead.


    The WSDL and XSD files are kept for historical reference only:


    - [Reseller-to-supplier WSDL](resources/api_specs/wsdl/tgds-reseller-to-supplier.wsdl)

    - [Supplier-to-reseller WSDL](resources/api_specs/wsdl/tgds-supplier-to-reseller.wsdl)

    - [API XSD](resources/api_specs/xsd/api.xsd)'
  humanURL: https://docs.viator.com/partner-api/technical/
  baseURL: https://api.viator.com/partner
  tags:
  - Deprecated
  properties:
  - type: OpenAPI
    url: openapi/viator-deprecated-api-openapi.yml
  - type: Documentation
    url: https://docs.viator.com/partner-api/technical/
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Products
  - type: PostmanCollection
    url: collections/Viator-Merchant-API-v2.postman_collection.json
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Availability
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Bookings
  - type: PostmanCollection
    url: collections/Viator-Affiliate-Booking-API-v2.postman_collection.json
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Payments
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Attractions
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Auxiliary
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/api-overview/
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/connectivity-overview/index.html
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/sapi-manual-latest/
  - type: Documentation
    url: https://docs.viator.com/partner-api/merchant/technical/
  - type: Documentation
    url: https://docs.viator.com/partner-api/affiliate/technical/
- aid: viator:viator-deprecated-services-api
  name: Viator Deprecated services API
  description: Deprecated services
  humanURL: https://docs.viator.com/partner-api/technical/
  baseURL: https://api.viator.com/partner
  tags:
  - Deprecated services
  properties:
  - type: OpenAPI
    url: openapi/viator-deprecated-services-api-openapi.yml
  - type: Documentation
    url: https://docs.viator.com/partner-api/technical/
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Products
  - type: PostmanCollection
    url: collections/Viator-Merchant-API-v2.postman_collection.json
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Availability
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Bookings
  - type: PostmanCollection
    url: collections/Viator-Affiliate-Booking-API-v2.postman_collection.json
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Payments
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Attractions
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Auxiliary
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/api-overview/
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/connectivity-overview/index.html
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/sapi-manual-latest/
  - type: Documentation
    url: https://docs.viator.com/partner-api/merchant/technical/
  - type: Documentation
    url: https://docs.viator.com/partner-api/affiliate/technical/
- aid: viator:viator-general-services-api
  name: Viator General services API
  description: General services
  humanURL: https://docs.viator.com/partner-api/technical/
  baseURL: https://api.viator.com/partner
  tags:
  - General services
  properties:
  - type: OpenAPI
    url: openapi/viator-general-services-api-openapi.yml
  - type: Documentation
    url: https://docs.viator.com/partner-api/technical/
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Products
  - type: PostmanCollection
    url: collections/Viator-Merchant-API-v2.postman_collection.json
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Availability
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Bookings
  - type: PostmanCollection
    url: collections/Viator-Affiliate-Booking-API-v2.postman_collection.json
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Payments
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Attractions
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Auxiliary
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/api-overview/
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/connectivity-overview/index.html
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/sapi-manual-latest/
  - type: Documentation
    url: https://docs.viator.com/partner-api/merchant/technical/
  - type: Documentation
    url: https://docs.viator.com/partner-api/affiliate/technical/
- aid: viator:viator-payments-api
  name: Viator Payments API
  description: The Payments API from Viator — 1 operation(s) for payments.
  humanURL: https://docs.viator.com/partner-api/technical/
  baseURL: https://api.viator.com/partner
  tags:
  - Payments
  properties:
  - type: OpenAPI
    url: openapi/viator-payments-api-openapi.yml
  - type: Documentation
    url: https://docs.viator.com/partner-api/technical/
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Products
  - type: PostmanCollection
    url: collections/Viator-Merchant-API-v2.postman_collection.json
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Availability
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Bookings
  - type: PostmanCollection
    url: collections/Viator-Affiliate-Booking-API-v2.postman_collection.json
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Payments
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Attractions
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Auxiliary
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/api-overview/
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/connectivity-overview/index.html
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/sapi-manual-latest/
  - type: Documentation
    url: https://docs.viator.com/partner-api/merchant/technical/
  - type: Documentation
    url: https://docs.viator.com/partner-api/affiliate/technical/
- aid: viator:viator-product-services-api
  name: Viator Product services API
  description: Product services
  humanURL: https://docs.viator.com/partner-api/technical/
  baseURL: https://api.viator.com/partner
  tags:
  - Product services
  properties:
  - type: OpenAPI
    url: openapi/viator-product-services-api-openapi.yml
  - type: Documentation
    url: https://docs.viator.com/partner-api/technical/
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Products
  - type: PostmanCollection
    url: collections/Viator-Merchant-API-v2.postman_collection.json
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Availability
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Bookings
  - type: PostmanCollection
    url: collections/Viator-Affiliate-Booking-API-v2.postman_collection.json
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Payments
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Attractions
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Auxiliary
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/api-overview/
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/connectivity-overview/index.html
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/sapi-manual-latest/
  - type: Documentation
    url: https://docs.viator.com/partner-api/merchant/technical/
  - type: Documentation
    url: https://docs.viator.com/partner-api/affiliate/technical/
- aid: viator:viator-products-api
  name: Viator Products API
  description: The Products API from Viator — 7 operation(s) for products.
  humanURL: https://docs.viator.com/partner-api/technical/
  baseURL: https://api.viator.com/partner
  tags:
  - Product
  tags_raw:
  - Products
  properties:
  - type: OpenAPI
    url: openapi/viator-products-api-openapi.yml
  - type: Documentation
    url: https://docs.viator.com/partner-api/technical/
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Products
  - type: PostmanCollection
    url: collections/Viator-Merchant-API-v2.postman_collection.json
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Availability
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Bookings
  - type: PostmanCollection
    url: collections/Viator-Affiliate-Booking-API-v2.postman_collection.json
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Payments
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Attractions
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Auxiliary
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/api-overview/
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/connectivity-overview/index.html
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/sapi-manual-latest/
  - type: Documentation
    url: https://docs.viator.com/partner-api/merchant/technical/
  - type: Documentation
    url: https://docs.viator.com/partner-api/affiliate/technical/
- aid: viator:viator-reservation-system-apis-api
  name: Viator Reservation system APIs API
  description: "This section describes all the possible services, some of which are mandatory, that reservation systems can\
    \ develop to integrate with Viator. \n\nAll API requests made by Viator to the reservation system are specified. The reservation\
    \ system will respond to Viator requests in a synchronous manner, responding as per specification. Both request and response\
    \ formats are described in detail in subsequent sections of this document.\n\n### Authentication\n\nThese endpoints support\
    \ two authentication mechanisms: the legacy body-embedded `ApiKey` field, which is always required in the request payload\
    \ for v1 APIs, or the `X-Api-Key` header used by the v2 APIs. The header option was added so existing partners could migrate\
    \ to header-based authentication without changing endpoints.\n\n### BookingCutoff and Capacity elements\n\nThe [Availability\
    \ response](#tag/Reservation-system-APIs/operation/availability) includes two elements used to determine whether a booking\
    \ can proceed:\n\n- **`BookingCutoff`** communicates the point in time after which a tour option may no longer be purchased.\
    \ Exactly one of its three child elements must be provided: `DateTime` (a timezone-qualified timestamp), `ProductDateTime`\
    \ (a timestamp in the product's own local time, with no timezone offset), or `NotApplicable` (a boolean, `true` if no\
    \ cut-off exists for the product option).\n- **`Capacity`** communicates the remaining places available for Viator to\
    \ book. Its `Simple` child element holds `Remaining` (the number of places left) and `ConsumedBy` (the age bands — `ADULT`,\
    \ `CHILD`, `INFANT`, `YOUTH`, `SENIOR` — that draw down on those places), which lets specific age bands (e.g. infants)\
    \ be excluded from consuming capacity.\n\nBoth elements are part of the [Availability response schema](#tag/Reservation-system-APIs/operation/availability)\
    \ — see that operation for the full field definitions."
  humanURL: https://docs.viator.com/partner-api/technical/
  baseURL: https://api.viator.com/partner
  tags:
  - Reservation system APIs
  properties:
  - type: OpenAPI
    url: openapi/viator-reservation-system-apis-api-openapi.yml
  - type: Documentation
    url: https://docs.viator.com/partner-api/technical/
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Products
  - type: PostmanCollection
    url: collections/Viator-Merchant-API-v2.postman_collection.json
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Availability
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Bookings
  - type: PostmanCollection
    url: collections/Viator-Affiliate-Booking-API-v2.postman_collection.json
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Payments
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Attractions
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Auxiliary
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/api-overview/
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/connectivity-overview/index.html
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/sapi-manual-latest/
  - type: Documentation
    url: https://docs.viator.com/partner-api/merchant/technical/
  - type: Documentation
    url: https://docs.viator.com/partner-api/affiliate/technical/
- aid: viator:viator-support-services-api
  name: Viator Support services API
  description: Support services
  humanURL: https://docs.viator.com/partner-api/technical/
  baseURL: https://api.viator.com/partner
  tags:
  - Support Services
  tags_raw:
  - Support services
  properties:
  - type: OpenAPI
    url: openapi/viator-support-services-api-openapi.yml
  - type: Documentation
    url: https://docs.viator.com/partner-api/technical/
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Products
  - type: PostmanCollection
    url: collections/Viator-Merchant-API-v2.postman_collection.json
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Availability
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Bookings
  - type: PostmanCollection
    url: collections/Viator-Affiliate-Booking-API-v2.postman_collection.json
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Payments
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Attractions
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Auxiliary
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/api-overview/
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/connectivity-overview/index.html
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/sapi-manual-latest/
  - type: Documentation
    url: https://docs.viator.com/partner-api/merchant/technical/
  - type: Documentation
    url: https://docs.viator.com/partner-api/affiliate/technical/
- aid: viator:viator-taxonomy-services-api
  name: Viator Taxonomy services API
  description: Taxonomy services
  humanURL: https://docs.viator.com/partner-api/technical/
  baseURL: https://api.viator.com/partner
  tags:
  - Taxonomy services
  properties:
  - type: OpenAPI
    url: openapi/viator-taxonomy-services-api-openapi.yml
  - type: Documentation
    url: https://docs.viator.com/partner-api/technical/
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Products
  - type: PostmanCollection
    url: collections/Viator-Merchant-API-v2.postman_collection.json
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Availability
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Bookings
  - type: PostmanCollection
    url: collections/Viator-Affiliate-Booking-API-v2.postman_collection.json
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Payments
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Attractions
  - type: APIReference
    url: https://docs.viator.com/partner-api/technical/#tag/Auxiliary
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/api-overview/
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/connectivity-overview/index.html
  - type: Documentation
    url: https://docs.viator.com/supplier-api/technical/sapi-manual-latest/
  - type: Documentation
    url: https://docs.viator.com/partner-api/merchant/technical/
  - type: Documentation
    url: https://docs.viator.com/partner-api/affiliate/technical/


# --- truncated at 32 KB (38 KB total) ---
# Full source: https://artifacts.apis.io/viator/apis.yml

Viator API — frequently asked questions

Does Viator have an API?

Yes. APIs.io lists 17 APIs from Viator, including Viator Attraction services API, Viator Attractions API and Viator Auxiliary API, and 14 more.

Is there an OpenAPI specification for the Viator API?

Yes. APIs.io indexes 17 OpenAPI specifications for Viator, each linked for download from this page.

How do I authenticate with the Viator API?

Viator uses bearer-token authentication (apiKey · 3 schemes). The details are profiled on APIs.io as Viator Authentication.

Is the Viator API ready for AI agents?

Viator has a Kin Score of 49.7 out of 100 (developing) and an Agent Readiness score of 48.1 (agent-native), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/viator"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/viator/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/viator/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.