← Back to all docs

TrekkSoft API

TrekkSoft is a tour and activity booking platform for operators, powering an omni-channel booking engine, on-site POS, back office operations, Payyo payments, and a channel manager that distributes inventory to OTAs and resellers. An unofficial API lets you programmatically pull bookings, activities, availability, customers, and payments—and push updates like new reservations, availability changes, and voucher redemptions back into TrekkSoft.

By Alex KlarfeldMay 30, 2026
TrekkSoft API

What is TrekkSoft?

TrekkSoft is a tour and activity booking platform, founded in Interlaken, Switzerland, that powers thousands of activity providers worldwide. Operators use TrekkSoft to take bookings through a website booking engine, sell on-site with a mobile point of sale, run day-to-day operations in a back office tool, process payments through the integrated Payyo gateway, and distribute their inventory to online travel agencies and resellers through a channel manager.

Core product areas include:

  • Booking Engine (conversion-optimized website widget across desktop, tablet, and mobile)
  • Point of Sale (mobile/tablet checkout for in-store and on-site transactions)
  • Back Office Tool (centralized operations management and workflow automation)
  • Payyo Payment Gateway (integrated global payment processing)
  • Channel Manager (unified-API distribution to OTAs and marketplaces with automatic availability sync)
  • Agents and Resellers (partnership tools for travel agents and local resellers)

Common data entities:

  • Activities, Products, Timeslots, Capacities
  • Availability, Schedules, Sessions
  • Bookings, Baskets, Participants, Add-ons
  • Customers, Vouchers, Coupons
  • Payments, Refunds, Payouts (Payyo)
  • Channels, Resellers, Agents, Distribution Mappings

The TrekkSoft Integration Challenge

Operators run their entire revenue operation on TrekkSoft, but turning booking, availability, and payment data into reliable API-driven automation is harder than it looks:

  • Developer-account and partnership gates: API and channel-manager access is provisioned per operator, so credentials, scopes, and reseller mappings vary from one account to the next
  • Live availability is the hard part: OTAs need instant confirmation against real-time capacity, and availability logic is spread across schedules, timeslots, and per-channel rules
  • Multi-channel spread: the same inventory flows through the booking engine, POS, agents, and the channel manager—each with its own object shapes and identifiers to reconcile
  • Payment data lives in Payyo: settlements, refunds, and payouts are processed through a separate gateway that must be tied back to bookings for accurate reporting
  • Session-based authentication: the operator's own booking, customer, and payout history sits behind a logged-in back office that is not designed for headless automation
  • Coverage varies by module: webhook events, sandbox behavior, and endpoint availability differ across booking, availability, and distribution surfaces

How Supergood Creates TrekkSoft APIs

Supergood reverse-engineers authenticated back office flows alongside TrekkSoft's developer API and Payyo payment surfaces to deliver a resilient API layer for your TrekkSoft account—across bookings, availability, and distribution.

  • Handles username/password and session-based login securely, with automated refresh
  • Maintains session continuity with change detection across the booking engine, POS, and channel manager
  • Normalizes responses across activities, bookings, availability, customers, and Payyo payments so you integrate once
  • Reconciles inventory and availability across direct, agent, reseller, and OTA channels

Use TrekkSoft with AI agents: TrekkSoft MCP Server →

Getting Started

  • Schedule Integration Assessment

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

  • Supergood Generates and Validates Your API

We deliver a production-ready TrekkSoft adapter tailored to your account configuration and distribution setup.

  • Deploy with Monitoring

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

trekksoft

API Endpoints

Authentication

POST/authenticate

Authenticate to a TrekkSoft account with username/password or API credentials and obtain a session token for downstream calls.

Activities

GET/activities

List activities and products with details, pricing tiers, add-ons, and configured timeslots.

Availability

GET/availability

Retrieve real-time availability and remaining capacity for an activity across dates, sessions, and channels.

Bookings

GET/bookings

Pull bookings with participant, channel, status, and payment details filtered by date and activity.

Bookings

POST/create_booking

Create a booking or basket against a selected activity, timeslot, and participant set, returning a confirmation.

Payments

GET/payments

Pull payments, refunds, and payouts from the Payyo gateway and reconcile them against bookings.

Use Cases

Sync bookings and customers into your warehouse

- Pull bookings, participants, and add-ons across the booking engine, POS, and agent channels into one warehouse - Stream new-reservation and cancellation events to downstream BI and CRM tools - Reconcile customer and voucher records for unified guest reporting

Distribute live availability to OTAs and resellers

- Push real-time availability and capacity to OTAs and marketplaces for instant confirmation - Keep activity, pricing, and timeslot data in sync across direct, agent, and reseller channels - Detect overbooking risk before it reaches the customer

Reconcile Payyo payments and payouts

- Sync payments, refunds, and payouts from the Payyo gateway into accounting and AR systems - Match settlements back to their originating bookings and channels - Surface failed payments and pending refunds to operations workflows

Automate operations from the back office

- Push new bookings, reschedules, and voucher redemptions back into TrekkSoft without manual entry - Trigger guest communications and manifests from booking and timeslot changes - Update capacities and schedules programmatically as conditions change

Technical Specifications

Authentication

Username/password and API credentials handled in a managed, session-based login

Connectivity

Authenticated back office flows plus TrekkSoft's developer API and Payyo payment surfaces where exposed by the account

Response format

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

Rate limits

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

Session management

Automatic session refresh, re-login handling, and credential rotation

Data freshness

Near real-time pulls for bookings, availability, and payments 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, cancellations, availability changes, and payment events

Latency

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

Throughput

Horizontally scaled workers sized to multi-channel booking and distribution volume

Reliability

Retry, backoff, and idempotency keys for bookings, availability updates, and refunds

Adaptation

Continuous monitoring of TrekkSoft releases, channel-manager mappings, and account configuration drift

Frequently asked questions

Yes. Supergood normalizes bookings across the website booking engine, POS, agents, and channel-manager distribution, so reservations from every channel arrive in one consistent shape.

Yes. Availability and remaining capacity are surfaced in real time across dates, sessions, and channels, so OTAs and marketplaces can confirm bookings instantly against live inventory.

Payments, refunds, and payouts processed through the Payyo gateway are pulled and matched back to their originating bookings, so settlement and reporting stay reconciled.

Supergood works with your existing TrekkSoft account and authenticated sessions. Where the developer API or channel-manager access is provisioned for your account, we use it; otherwise we operate against the same authenticated surfaces your team already uses.

Your account is profiled against its activities, channels, and pricing configuration, and Supergood continuously monitors TrekkSoft releases and distribution mappings, adapting the adapter rather than forcing a generic schema.

Ready to get a real API?