The API Report CardAPI Index
Regiondo

Regiondo API

POS / Hospitality (Tours, Activities & Attractions Booking) · regiondo.com

A documented REST API covers bookings, availability, customers, and tickets, with webhooks for those events. Keys are provisioned per operator inside the Regiondo Pro dashboard, so ISVs need an operator account or partner agreement first. Docs are a PDF plus a sandbox Swagger explorer.

Last verified: July 2026Hospitality & Travel
API GRADE
C
VERIFIED JUL 2026

SCORECARD

ExistenceGOODA documented REST API (v1) covers bookings, products, availability, customers, and ticket lifecycle, plus webhooks.
AccessMIXEDKeys are provisioned per operator inside the Regiondo Pro dashboard; ISVs need an operator account or partner agreement first.
CoverageMIXEDBookings, products, customers, and tickets are covered; payment and refund events have no webhook, so integrators poll.
AuthMIXEDPer-tenant API keys generated under Shop Configuration in the operator dashboard; confirmations rely on a hosted Callback-URL.
Docs & DXPOORDocs are a downloadable PDF plus a sandbox Swagger explorer, not a maintained portal; rate limits live in support articles.
StabilityMIXEDThrottling behavior is discovered empirically; limits sit in support articles rather than the API spec.
MORE FROM THE REPORT CARD
Supergood: Regiondo has an API, with gaps. We cover what it's missing: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Regiondo scores C on the API Report Card. A documented REST API covers bookings, availability, customers, and tickets, with webhooks for those events. Keys are provisioned per operator inside the Regiondo Pro dashboard, so ISVs need an operator account or partner agreement first. Docs are a PDF plus a sandbox Swagger explorer.

Tried to integrate with Regiondo?
SOURCES
No self-serve developer signup - API keys are provisioned per-tenant inside an operator's Regiondo Pro dashboard, so ISVs must first have an operator account or partner agreement before they can integrate. support.regiondo.com
Documentation is delivered as a downloadable PDF plus a Swagger/explorer UI under sandbox-api.regiondo.com - not a modern dev portal with versioned changelogs, code samples, and SDKs comparable to Stripe/Square. sandbox-api.regiondo.com
Webhook surface is limited to Booking, Customer, and Ticket event types; finer-grained availability, payment, or refund event subscriptions require polling. support.regiondo.com
Async booking-confirmation pattern (Callback-URL) requires every integrator to stand up a public callback endpoint and handle out-of-order updates, instead of synchronous booking creation with idempotency keys. support.regiondo.com
Rate limits and SLA terms are documented in support articles ('API Limits') but are not surfaced in the OpenAPI spec; integrators discover throttling behavior empirically. support.regiondo.com
Channel/OTA distribution integrations (Viator, GetYourGuide, Musement, Expedia, Klook) are managed separately from the public REST API, requiring partners who want both ISV and reseller paths to do duplicate onboarding. linkedin.com
OCTO API alignment work has been publicly teased but is not yet the canonical surface - integrators have to choose between Regiondo's bespoke v1 REST and emerging OCTO standards. linkedin.com
Booking system reliability failures - merchants report migrating to Regiondo and losing bookings, eventually reverting to their previous supplier after the system would not work. trustpilot.com
Pricing/calculation bugs - one operator reported a GBP 30 activity totalling GBP 35.64 in checkout, with the booking math producing incorrect line items. trustpilot.com
Package-deal availability bugs - configured packages display as fully booked even with capacity, and re-break the day after support fixes them. trustpilot.com
Opaque combined pricing - subscription + monthly system-usage fee (~3% of gross revenue) + per-ticket fee makes total cost-of-ownership hard to forecast vs. flat-commission competitors like Bokun. bokun.io
Cancellation/commission policy - operators report owing full commissions to Regiondo even when the customer cancels the booking, leaving the operator out-of-pocket on no-shows. capterra.com
Long one-year contracts billed monthly with a 10% discount only on annual upfront payment - friction for operators wanting to test the platform. bokun.io
Support escalation gaps - multiple reviewers describe needing to be in constant contact with support, with some issues ultimately marked unresolved. softwareadvice.com
Consumer-facing complaints - end customers report tours cancelled post-payment with chatbot/operator support unreachable, eroding operator brand trust. trustpilot.com