Developers

Two APIs.

Suppliers push their catalog with one key. Every distributor reads availability and books through the same second API. A marketplace does not get its own route.
Suppliers     Authorization: Bearer vx_...
Distributors  Authorization: Bearer vd_...

Supplier routes are the same on /api/v1 and /api/suppliers/v1. The key belongs to one organization.

GET /api/v1/catalog

Products, images, descriptions, included items, categories, and 60 days of slots.

POST /api/v1/products

Create or replace a product, including photos and ticket types.

PUT /api/v1/products/:id/availability

Dates, times, remaining places, and a price for each category.

POST /api/v1/cart

Open a cart for a product, a departure, and quantities.

POST /api/v1/cart/:id/checkout

Attach the guest: name, email, phone, country.

POST /api/v1/cart/:id/confirm

Confirm the sale. No card number is stored.

GET /api/v1/bookings

Recent sales, including reference, status, and total.

GET /api/v1/intersport

Intersport catalog through Stayviax: massifs, stations, shops, and a shop catalog for a stay.

POST /api/v1/intersport?resource=confirm

Confirm an Intersport rental. Viax calls Stayviax. Stayviax calls Intersport.

POST /api/v1/intersport?resource=cancel

Cancel that rental with the Stayviax booking number and the Intersport id.

Intersport through Stayviax

Viax calls Stayviax from the server. The browser never sees that key. A catalog price is the price of the selected stay: the same day is 1 rental day, and the price is not multiplied by the number of days. While the response says preprod, do not publish those prices on a travel site and do not confirm a channel booking.

Authorization: Bearer vx_...

GET  /api/v1/intersport?resource=massifs&lang=fr
GET  /api/v1/intersport?resource=stations&massifId=17&lang=fr
GET  /api/v1/intersport?resource=shops&stationId=486&lang=fr
GET  /api/v1/intersport?resource=catalog&shopId=1652&startDate=2026-12-11&endDate=2026-12-11&lang=fr
POST /api/v1/intersport?resource=confirm
POST /api/v1/intersport?resource=cancel

Distributors

Viator, GetYourGuide, Tiqets and the others call these routes with their own key. Prices are in euros. A reservation is held for 60 minutes. The supplier id is the organization id.

Authorization: Bearer vd_...

GET  /api/distributors/v1/suppliers
GET  /api/distributors/v1/suppliers/{supplierId}/products
GET  /api/distributors/v1/products/{productId}
GET  /api/distributors/v1/availability?productId=&from=2026-10-03&to=2026-10-10
POST /api/distributors/v1/reservations
POST /api/distributors/v1/reservations/{reference}/cancel
POST /api/distributors/v1/bookings
POST /api/distributors/v1/bookings/{reference}/cancel

Channel adapters

Each marketplace adapter is isolated. Viax does not call Viator, GetYourGuide, Tiqets, or any other live marketplace until that channel's credential and specification are configured.

class ChannelAdapter {
  createProduct()
  updateAvailability()
  updatePricing()
  receiveBooking()
  cancelBooking()
}

Operator webhooks

Outbound events are prepared for booking.created, booking.cancelled, and distribution.error. Signing uses WEBHOOK_SIGNING_SECRET. Nothing is sent until an endpoint is stored for the organization. Create a key in the workspace under API. The secret is shown once.