← Back to all docs

Xola API

Xola is an online booking and management platform for tours, activities, and attractions, powering reservations, payments, marketing automation, POS ticketing, staff scheduling, and digital waivers. An API lets you programmatically pull orders, experiences, availability, customers, and payments—and push updates like new bookings, reschedules, and cancellations back into Xola, so your operator data is no longer trapped behind the booking portal.

By Alex KlarfeldMay 29, 2026
Xola API

What is Xola?

Xola is an online booking and management system for tours, activities, and attractions operators. Businesses use Xola to take online and walk-up reservations, process payments, run marketing automation and abandoned-booking recovery, coordinate staff and equipment, capture digital waivers, and distribute inventory to consumer marketplaces—managing the entire guest lifecycle from a single command center.

Core product areas include:

  • Online Booking & Checkout (mobile checkout, add-ons, coupons, cart recovery)
  • Command Center (bookings, waitlists, and availability operations hub)
  • Point-of-Sale & Ticketing (high-volume walk-up management and check-ins)
  • Marketing Automation (Xolabot revenue optimization and booking recapture)
  • Product Management, Staff Management, and Equipment Management
  • Digital Waivers, Reporting, Websites, and iOS/Android mobile apps

Common data entities:

  • Orders, Bookings, Items, Add-ons, Packages, Memberships
  • Experiences, Products, Schedules, Availability, Equipment
  • Customers, Guests, Waivers, Coupons, Gift Cards
  • Payments, Refunds, Transactions, Sellers, Staff

The Xola Integration Challenge

Operators run their entire reservation business on Xola, but getting that booking, guest, and payment data out cleanly and into automation is harder than it looks:

  • Application API Key gating: Building against the API requires a developer account and an issued Application API Key, so partnership and approval steps stand between you and your own data
  • Portal- and POS-driven workflows: Walk-up check-ins, waitlists, and equipment allocation live in the Command Center and mobile apps, not in a clean export
  • Distribution channel complexity: Inventory synced to Expedia, TripAdvisor, and other marketplaces creates orders from many sources that must be reconciled to one schedule
  • Availability and overbooking logic: Real-time slot, equipment, and capacity rules are intricate and easy to break with naive polling
  • Payment and refund handling: Transactions, deposits, and refunds carry seller-specific configuration that generic integrations mishandle
  • App Store fragmentation: 80+ point apps each cover a slice of the workflow, leaving no single normalized surface for your operator data

How Supergood Creates Xola APIs

Supergood reverse-engineers Xola's authenticated REST surface, Command Center flows, and App Store webhooks to deliver a resilient, normalized API layer over your Xola seller account—so your booking, guest, and payment data is available programmatically without stitching together point apps.

  • Handles X-API-KEY application keys and authenticated sessions securely, including MFA where enforced
  • Maintains session continuity with automated refresh and change detection
  • Normalizes orders, experiences, availability, customers, and payments so you integrate once against consistent objects
  • Reconciles bookings across direct, walk-up POS, and distribution-channel sources into one schedule

Use Xola with AI agents: Xola MCP Server →

Getting Started

  • Schedule Integration Assessment

Book a 30-minute session to confirm your Xola modules, distribution channels, and authentication model.

  • Supergood Generates and Validates Your API

We deliver a production-ready Xola adapter tailored to your seller account, products, and payment configuration.

  • Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as Xola evolves.

xola

API Endpoints

Authentication

POST/authenticate

Authenticate to a Xola seller account with an Application API Key (X-API-KEY) and obtain a session for downstream calls.

Orders

GET/orders

List orders and bookings across experiences, packages, and distribution channels with filters for date, status, and source.

Orders

POST/create_order

Create a booking for one or more experiences or packages, including add-ons, customer details, and payment.

Experiences

GET/experiences

Retrieve experiences, products, schedules, and configuration for a seller account.

Availability

GET/availability

Pull real-time slot, capacity, and equipment availability for an experience and date range.

Customers

GET/customers

List customers and guest records with booking history, waivers, and contact details.

Use Cases

Sync bookings and guest data into your warehouse

- Pull orders, items, and customer records from every channel into a single warehouse - Reconcile direct, walk-up POS, and distribution-channel bookings to one schedule - Stream booking and cancellation events to downstream BI and CRM tools

Automate availability and inventory updates

- Read real-time slot, capacity, and equipment availability per experience - Push schedule and capacity changes without Command Center clicks - Prevent overbooking by reconciling availability across marketplaces

Reconcile payments and refunds

- Sync transactions, deposits, and refunds into accounting and AR systems - Match payments to orders and sellers for unified financial reporting - Surface chargebacks and failed payments to retention workflows

Power marketing and guest experience automation

- Trigger abandoned-booking recovery and upsell flows from order events - Sync customers, waivers, and check-in status to messaging tools - Feed conversion data to analytics and ad platforms

Technical Specifications

Authentication

Application API Key via X-API-KEY header (or apiKey query param) handled in a managed session

Connectivity

Xola's RESTful, resource-oriented API plus authenticated Command Center flows and App Store webhooks

Response format

Normalized JSON across Orders, Experiences, Availability, Customers, and Payments objects

Rate limits

Adaptive throttling tuned to your seller account to avoid Xola-side limits

Session management

Automatic session refresh, key rotation, and re-auth on expiry

Data freshness

Near real-time pulls for orders and availability with optional scheduled batch syncs

Security

Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging

Webhooks

Event-style callbacks for new bookings, reschedules, cancellations, refunds, and check-ins

Latency

Sub-second reads on cached entities; multi-second writes when posting bookings and payments

Throughput

Horizontally scaled workers sized to high-volume booking and walk-up POS traffic

Reliability

Retry, backoff, and idempotency keys for order creation, payments, and refunds

Adaptation

Continuous monitoring of Xola API releases, App Store changes, and distribution-channel updates

Frequently asked questions

Building directly against Xola requires a developer account and an issued Application API Key. Supergood works with your existing Xola seller credentials and keys, handling the auth and session management so you don't have to maintain a custom integration.

Yes. The normalized API supports listing orders and creating, updating, and cancelling bookings for experiences and packages, alongside read access to experiences, availability, customers, and payments.

Supergood reconciles orders from direct checkout, walk-up POS, and connected distribution channels into one normalized schedule, so multi-source bookings map to a single availability view.

Yes. Transactions, deposits, refunds, and digital waiver records are exposed through the same normalized API surface, alongside orders and customers.

Supergood continuously monitors Xola API releases, App Store updates, and distribution-channel changes, adapting the adapter automatically so your integration keeps working.

Ready to get a real API?