← Back to all docs

Peek Pro API

Peek Pro is the booking and operations platform that experience operators—tour, activity, rental, and attraction businesses—run to sell, schedule, and manage their bookings. An unofficial API lets you programmatically pull bookings, customers, activities, availability, and payments, and push updates like new reservations, reschedules, and cancellations back into Peek Pro—without waiting on OCTO reseller approval or building against a partner-gated surface.

By Alex KlarfeldMay 30, 2026
Peek Pro API

What is Peek Pro?

Peek Pro is booking and operations software from Peek Travel Inc. used by thousands of experience operators—tour, activity, rental, class, and attraction businesses—to sell, schedule, and manage their bookings. Operators run online booking, an in-person point of sale, dynamic pricing, add-ons and bundles, payments, automated marketing, and reporting on Peek Pro, while also reaching consumers through the Peek.com marketplace and reseller channels.

Core product areas include:

  • Online Booking (real-time availability, calendar, and a configurable checkout)
  • Point of Sale (in-person bookings, walk-ups, and on-site sales)
  • Dynamic Pricing, Add-ons, and Bundles for upselling and seasonal rates
  • Payments (split payments, Apple & Google Pay, invoicing) and abandoned-cart recovery
  • Marketing, review management, and reporting/analytics
  • Reseller distribution via the OCTO API (TourDesk, Tiqets, Klook, and other channels)

Common data entities:

  • Bookings, Reservations, Order Items, Add-ons
  • Activities/Tours, Products, Options, Availability
  • Customers, Guests, Contacts
  • Payments, Refunds, Invoices, Pricing
  • Manifests, Schedules, Capacity

The Peek Pro Integration Challenge

Operators run their entire schedule, cash flow, and customer base on Peek Pro every day, but getting that data out programmatically is harder than it looks:

  • Reseller-gated API: Peek's public API is the OCTO Reseller API, built for distribution partners selling inventory—not for an operator who wants full read/write access to their own bookings, customers, and payments
  • Access approval: OCTO API keys require a Request Access flow and partnership agreement before any Bearer token is issued
  • Spec-scoped surface: the OCTO standard covers products, availability, and bookings for resale, so operator-owned data like customer records, payment detail, and marketing lives behind the portal, not the API
  • Capability flags: pricing and webhooks are opt-in OCTO capabilities negotiated via request headers, and coverage varies by what the supplier has enabled
  • Portal-only workflows: dynamic pricing rules, add-on configuration, abandoned-cart recovery, and reporting are managed in the Peek Pro dashboard with no documented API
  • Marketplace coupling: inventory is shared across Peek.com and reseller channels, so booking and availability state must stay consistent across surfaces you don't control

How Supergood Creates Peek Pro APIs

Supergood reverse-engineers the authenticated Peek Pro dashboard alongside the OCTO Reseller API to deliver a resilient API layer over your own Peek Pro account—covering the operator-owned data the reseller spec leaves out.

  • Handles operator login plus MFA securely in a managed session
  • Maintains session continuity with automatic refresh and change detection
  • Normalizes bookings, customers, activities, availability, and payments into consistent JSON so you integrate once
  • Reconciles state across the dashboard, the OCTO surface, and the Peek.com marketplace

Use Peek Pro with AI agents: Peek Pro MCP Server →

Getting Started

  • Schedule Integration Assessment

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

  • Supergood Generates and Validates Your API

We deliver a production-ready Peek Pro adapter tailored to your account, inventory, and entitlements.

  • Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as Peek Pro evolves.

peek pro

API Endpoints

Authentication

POST/authenticate

Authenticate to a Peek Pro account using operator credentials and MFA, and obtain a session token for downstream calls.

Bookings

GET/bookings

List bookings and reservations with filters for activity, date range, channel, and status.

Bookings

POST/create_booking

Create a new reservation against an activity and availability slot, including add-ons and customer detail.

Availability

GET/availability

Retrieve real-time availability and capacity for activities across scheduled dates and times.

Customers

GET/customers

Pull customer and guest records, including contact detail and booking history.

Payments

GET/payments

Retrieve payments, refunds, and invoice detail tied to bookings and orders.

Use Cases

Sync bookings and availability into your own systems

- Pull bookings, reservations, and add-ons from Peek Pro into a data warehouse or CRM - Stream availability and capacity changes to downstream scheduling and ops tools - Keep activity and product catalogs in sync across channels

Unify customer and payment data

- Consolidate customer and guest records across activities into a single profile - Reconcile payments, refunds, and invoices against bookings for finance reporting - Feed marketing tools with purchase history and contact detail

Automate reservation operations

- Create, reschedule, and cancel reservations programmatically without portal clicks - Trigger manifests and capacity updates when bookings change - Apply add-ons and pricing rules at booking time

Keep marketplace and reseller channels consistent

- Reconcile inventory across Peek.com, the OCTO reseller API, and direct booking - Detect overbooking and capacity conflicts across distribution surfaces - Surface channel-level booking and revenue data for reporting

Technical Specifications

Authentication

Operator credentials plus MFA handled in a managed session; OCTO Bearer tokens used where the reseller surface applies

Connectivity

Authenticated Peek Pro dashboard flows plus the OCTO Reseller API over HTTPS where exposed

Response format

Normalized JSON across Bookings, Availability, Customers, Activities, and Payments objects

Rate limits

Adaptive throttling tuned to your account to avoid Peek-side limits

Session management

Automatic session refresh, MFA replay handling, and credential rotation

Data freshness

Near real-time pulls for bookings 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 booking confirmations, updates, and cancellations, aligned with OCTO webhook capabilities

Latency

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

Throughput

Horizontally scaled workers sized to peak-season booking volume

Reliability

Retry, backoff, and idempotency keys for bookings, reschedules, and refunds

Adaptation

Continuous monitoring of Peek Pro dashboard and OCTO API changes with automatic adjustment

Frequently asked questions

Peek publishes the OCTO Reseller API, which is built for distribution partners reselling inventory and requires a Request Access partnership before a Bearer token is issued. It does not give an operator full read/write access to their own customers, payments, and portal-only workflows. Supergood works against your own authenticated Peek Pro account to cover that operator-owned data.

No. Supergood operates against your existing Peek Pro account and authenticated sessions. We use the OCTO surface only where it's already available to you; the operator-owned data flows through the authenticated dashboard.

Yes. The API supports read and write, so you can create reservations, apply add-ons, reschedule, and cancel programmatically, with idempotency safeguards on write operations.

Supergood reconciles booking and availability state across the dashboard, the OCTO reseller surface, and the Peek.com marketplace, and can surface capacity conflicts before they become overbookings.

Where the supplier has enabled the OCTO webhooks capability, Supergood subscribes to booking confirmation, update, and cancellation events; otherwise we deliver equivalent event callbacks through change detection on the authenticated surface.

Ready to get a real API?