How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

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 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 — deprecatedXML (`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) — deprecatedThe 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)

Viator Deprecated API is one of 17 APIs that Viator publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Deprecated. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 4 operations across 4 paths, and defines 17 schemas. It is described by OpenAPI 3.2.0.

Requests are made against a single base URL, https://your-reservation-system.example.com.

4 operations 4 paths 17 schemas 4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
Base URL
https://api.viator.com/partner
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Viator Deprecated API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-Api-Key (ApiKeyHeader).

Paths & Operations 4

Across 4 paths, the API surfaces 4 operations — 4 POST. Each is listed below with its method, path, parameters, and response codes.

Deprecated 4

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 ne…

POST
/availability
Real-time Availability
availability body → 200
POST
/batch-availability
Batch Availability
batchAvailability body → 200
POST
/batch-pricing
Batch Pricing
batchPricing body → 200
POST
/availabilitynotification2
Availability Notification 2
availabilityNotification2 body → 200

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are RequestResponseBase (5 properties), TourOptionBase (4 properties), TourLanguage (2 properties), RequestStatus (2 properties). Each schema is shown below with its type and property counts.

RequestResponseBase
object
Request Response Base.
5 properties 4 required
Price
object
Holds the information regarding the price for the associated Tour that was retrieved from the API.
2 properties 2 required
AvailabilityRequest
Root element for Real-time Availability Request
BatchPricingResponse
Root element for Batch Pricing Response
LanguageOption
string
BatchAvailabilityRequest
Root element for Batch Availability Request
RequestStatus
object
Request status root element. Holds the status information for the requested transaction.
2 properties 1 required
BatchPricingRequest
Root element for Batch Pricing Request
ResponseBase
AvailabilityNotification2Response
Root element for Availability Notification 2 Response
AvailabilityNotification2Request
Root element for Availability Notification 2 Request
TourLanguage
object
Holds the language of a tour.
2 properties 2 required
BatchAvailabilityResponse
Root element for Batch Availability Response
TourOptionItem
AvailabilityResponse
Root element for Real-time Availability Response
TourOptionBase
object
Tour option root element. Holds details pertaining to each of the product (tour) options (including default if no tour options exist).
4 properties
VersionTag
Version tag root element. Specifies the version for each changed DateAvailability. Version tagging allows availability responses to be tagged with one of: a ti…

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

viator-deprecated-api-openapi.yml Raw ↑

Other APIs Viator publishes across the network.

Viator Attraction services API
Viator Attractions API
Viator Auxiliary API
Viator Availability API
Viator Booking services API
Viator Bookings API
Viator Deprecated services API
Viator General services API
Viator Payments API
Viator Product services API
Viator Products API
Viator Reservation system APIs API
Where this information came from

This is an independent, third-party profile of Viator Deprecated API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.