← Back to all docs

Regiondo API

Regiondo is an all-in-one booking platform for tours, activities, and attractions, handling online reservations, payments, POS, ticket scanning, and distribution across 200+ OTAs through its channel manager. Its API lets suppliers programmatically pull products, availability, orders, bookings, tickets, and vouchers—and push actions like cancellations and ticket-code updates back into Regiondo, with booking confirmations delivered to a configurable callback URL.

By Alex KlarfeldMay 30, 2026
Regiondo API

What is Regiondo?

Regiondo is an all-in-one booking software platform built for the travel and leisure industry, enabling tours, activities, attractions, and destinations to manage reservations, accept payments, and distribute their offerings across multiple sales channels. Operators use Regiondo to take online bookings, process payments in multiple currencies, run an on-site POS, scan tickets, manage resources, and sell through 200+ OTA connections such as GetYourGuide, Viator, and Civitatis via its channel manager.

Core product areas include:

  • Booking System and Website Builder with integrated online reservations
  • Payment processing in multiple currencies (credit cards, PayPal, cash)
  • Channel Manager distributing to OTAs like GetYourGuide, Viator, and Civitatis
  • POS system for on-site and mobile bookings
  • Ticket scanning, resource management, and marketing tools
  • CRM, sales reporting, and analytics, plus Zapier and CMS integrations

Common data entities:

  • Products, Categories, Options, Time Slots, Availability
  • Orders, Bookings, Tickets, Ticket Codes, Cancellations
  • Customers, Payments, Commissions, Vouchers
  • Channels, OTA connections, and reseller mappings

The Regiondo Integration Challenge

Operators run daily reservation and ticketing workloads on Regiondo, but turning its supplier API and dashboard-driven workflows into reliable automation is non-trivial:

  • HMAC request signing: every call must carry X-API-HASH, X-API-TIME, and X-API-ID headers computed from public and private keys, with clock-synced timestamps
  • Supplier-scoped access: the API is designed for Regiondo suppliers, so coverage and entitlements differ from reseller and OTA-facing flows
  • Callback-driven confirmations: tickets and booking confirmations arrive asynchronously on a Callback-URL configured in the dashboard, requiring a listener to stay in sync
  • Cancellation constraints: ticket-code cancellations apply only to bookings placed via the API, so reconciling against OTA-originated bookings takes extra logic
  • Voucher and payment-status nuances: bookings with a Voucher payment status carry a separate type and are excluded by default from standard booking responses
  • Channel sprawl: with 200+ OTA connections, availability, pricing, and ticket data must stay consistent across many downstream channels

How Supergood Creates Regiondo APIs

Supergood handles Regiondo's HMAC-signed supplier API and dashboard-driven callback flows to deliver a resilient, normalized API layer for your Regiondo account—across products, availability, orders, tickets, and vouchers.

  • Computes and rotates X-API-HASH, X-API-TIME, and X-API-ID headers from your public and private keys, keeping the private key server-side
  • Receives Callback-URL events for confirmed bookings and generated tickets and reconciles them against your data
  • Normalizes JSON responses across products, orders, tickets, availability, and vouchers so you integrate once
  • Handles voucher and OTA-originated booking types so reconciliation stays complete across channels

Use Regiondo with AI agents: Regiondo MCP Server →

Getting Started

  • Schedule Integration Assessment

Book a 30-minute session to confirm your products, channels, and API key setup.

  • Supergood Generates and Validates Your API

We deliver a production-ready Regiondo adapter tuned to your supplier account and callback configuration.

  • Deploy with Monitoring

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

regiondo

API Endpoints

Authentication

POST/authenticate

Establish an authenticated session using your Regiondo public/private keys with HMAC-signed X-API-HASH, X-API-TIME, and X-API-ID headers.

Catalog

GET/products

List products, categories, options, and pricing configured in your Regiondo supplier account.

Catalog

GET/availability

Retrieve availability and time slots for products across dates to drive booking and channel sync.

Bookings

GET/orders

Pull orders and bookings, including sold items, ticket codes, calculated amounts, and commissions, with type and status filters.

Bookings

POST/create_order

Place a new booking against a product and time slot, returning order and ticket details once confirmed.

Tickets

POST/cancel_tickets

Cancel sold tickets by reference id or ticket code for bookings placed via the API.

Use Cases

Sync products, availability, and pricing to channels

- Pull products, categories, and options from Regiondo into your own storefront or data warehouse - Push availability and time-slot data to downstream channels and marketplaces - Keep pricing and option configuration consistent across 200+ OTA connections

Automate booking and ticketing operations

- Stream confirmed bookings and generated tickets from the Callback-URL into your operations tools - Pull orders with ticket codes, calculated amounts, and commissions for reporting - Trigger ticket-code cancellations for API-placed bookings without dashboard clicks

Reconcile payments, vouchers, and commissions

- Reconcile orders, payments, and disbursements into accounting and AR systems - Surface voucher-type bookings that are excluded from default booking responses - Match OTA commissions and net amounts against payout records

Build a unified attractions data layer

- Consolidate customers, bookings, and ticket scans across products into one customer 360 - Feed visitor and sales analytics into BI and marketing tools - Automate post-booking communications and resource scheduling

Technical Specifications

Authentication

HMAC request signing with X-API-HASH, X-API-TIME, and X-API-ID headers derived from public/private keys, managed server-side

Connectivity

Regiondo supplier REST API (base /v1) plus dashboard-configured Callback-URL events, surfaced through a normalized layer

Response format

JSON for all responses including data and errors, normalized across products, orders, tickets, and vouchers

Rate limits

Adaptive throttling tuned to your supplier account to avoid Regiondo-side limits

Session management

Automatic timestamp/HMAC regeneration and credential rotation with private keys never exposed in calls

Data freshness

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

Security

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

Webhooks

Callback-URL events for confirmed bookings and generated tickets, configurable under Shop Configuration in the dashboard

Latency

Sub-second reads on cached catalog and availability; multi-second writes when placing or cancelling bookings

Throughput

Horizontally scaled workers sized to peak booking and channel-sync volume

Reliability

Retry, backoff, and idempotency handling for order creation and ticket cancellations

Adaptation

Continuous monitoring of Regiondo API versions, callback changes, and OTA channel configuration drift

Frequently asked questions

Regiondo uses HMAC-based request signing. Each call includes X-API-HASH, X-API-TIME, and X-API-ID headers computed from your public and private keys. Supergood generates and rotates these server-side and never sends your private key in calls.

Yes. Regiondo delivers booking confirmations and generated tickets to a Callback-URL you configure in the dashboard. Supergood receives those callback events and reconciles them against order data so your systems stay in sync.

Bookings with a Paid (voucher) payment status carry the type voucher, and the default bookings response returns only standard booking-type records. Supergood surfaces voucher-type bookings explicitly so reconciliation stays complete.

Ticket-code cancellations apply to bookings placed via the API. Supergood handles cancellation by reference id or ticket code and reconciles results against OTA-originated bookings that follow different rules.

Yes. Regiondo's channel manager distributes to 200+ OTAs such as GetYourGuide, Viator, and Civitatis. Supergood keeps products, availability, and pricing consistent across those channels through the normalized API layer.

Ready to get a real API?