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 Payments API

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

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

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

This API exposes 1 operation across 1 path, and defines 8 schemas. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against 2 base URLs: https://api.viator.com/partner, https://api.sandbox.viator.com/partner.

1 operations 1 paths 8 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

Viator Payments API declares 1 security scheme for authenticating requests. An API key is passed in the header as exp-api-key (API-key). By default, every request must be authenticated.

Paths & Operations 1

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

Payments 1
POST
/v1/checkoutsessions/{sessionToken}/paymentaccounts
/v1/checkoutsessions/{sessionToken}/paymentaccounts
paymentsCreateToken 5 params body → 200404

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are CreditCard (8 properties), CreditCardRequest (6 properties), Address (2 properties), PaymentAccounts (1 property). Each schema is shown below with its type and property counts.

VaultCardRequest
object
The card submission payload.
1 property 1 required
CreditCardRequest
object
PCI sensitive details for a debit or credit card and relevant metadata.
6 properties 6 required
PaymentAccounts
object
1 property
AccountMetaData
object
1 property
VaultPaymentResponse
object
1 property 1 required
Address
object
Minimal billing address details for cardholder
2 properties 2 required
PaymentAccountsRequest
object
Wrapper element around payment data.
1 property 1 required
CreditCard
object
8 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

viator-payments-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 API
Viator Deprecated services API
Viator General services 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 Payments 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.