Viator · OpenAPI Overlay 1.0.0

API Evangelist enhancements for the Viator Merchant API v1

3 actions 3 updates update extends openapi/viator-merchant-api-v1-openapi.json

Generated by API Evangelist Written by API Evangelist tooling for Viator's API. It is a proposal applied on top of the contract, not a document Viator publishes.

View Overlay File View on GitHub Overlay Specification

What the actions change

x-lifecycle-statusx-superseded-byx-notex-apievangelist-providerx-still-publishedx-apievangelist-artifacts

Targets 3

$.info

$.components.securitySchemes['Legacy-API-key']

$.paths['/merchant/cancellation'].post

OpenAPI Overlay

overlay: 1.0.0
info:
  title: API Evangelist enhancements for the Viator Merchant API v1
  version: 1.0.0
extends: openapi/viator-merchant-api-v1-openapi.json
x-generated: '2026-07-28'
x-method: generated
x-source: >-
  Derived from lifecycle/viator-lifecycle.yml and conventions/viator-conventions.yml. The original
  specification is preserved verbatim in openapi/.
actions:
- target: $.info
  update:
    x-apievangelist-provider: viator
    x-lifecycle-status: superseded
    x-superseded-by: openapi/viator-partner-api-v2-openapi.json
    x-still-published: true
    x-note: >-
      Legacy v1 merchant contract, still published by Viator but superseded by the Partner API v2.
      New integrations should build against v2.
    x-apievangelist-artifacts:
      lifecycle: lifecycle/viator-lifecycle.yml
      conventions: conventions/viator-conventions.yml
      authentication: authentication/viator-authentication.yml
- target: $.components.securitySchemes['Legacy-API-key']
  update:
    x-lifecycle-status: legacy
    x-note: >-
      Passing the API key as an apiKey query-string parameter exposes the credential in logs,
      referrers and browser history. The exp-api-key header scheme should be used instead.
- target: $.paths['/merchant/cancellation'].post
  update:
    x-superseded-by: [cancelBooking, cancelBookingQuote]