Rezdy API
Three documented REST APIs (Supplier, Agent, RezdyConnect) plus booking webhooks live at developers.rezdy.com. Full access is gated to the top-tier plan, with per-account keys passed as URL query parameters. No published SDKs and no bulk historical export exist.
Frequently asked questions
Rezdy scores C on the API Report Card. Three documented REST APIs (Supplier, Agent, RezdyConnect) plus booking webhooks live at developers.rezdy.com. Full access is gated to the top-tier plan, with per-account keys passed as URL query parameters. No published SDKs and no bulk historical export exist.
Rezdy has an official API, but teams routinely hit its limits: gated access, partial coverage, or paid tiers. Most end up supplementing it with exports or an unofficial API layer like Supergood.
Rezdy is a cloud-based reservation, channel management, and payments platform purpose-built for tour, activity, attraction, charter, rental, and shuttle operators.
Vertical: tours, activities, and experiences (TAA) operating software, a niche of the broader travel-tech stack. Classified as 'misc' because Supergood's vertical taxonomy does not include a dedicated travel/TAA bucket. A tour operator (say, a kayak rental and guided tour business in Sydney) signs up for Rezdy, builds their product catalog (multi-day kayak rental, half-day guided harbor tour, sunset tour) with pricing tiers, seasonal availability, resource constraints (kayaks, guides), and add-ons (dry bags, paddle upgrades).
6/10. Rezdy publicly cites 'thousands of operators across 100+ countries' and ~93 employees as of early 2026, and the company raised ~$15.3M in venture funding from Bailador, Microequities, and Grand Prix Capital before being acquired by Checkfront in June 2023.
Yes, for the thousands of tour, activity, and experience operators that run on Rezdy, the platform is the single system of record for the entire bookable-inventory and revenue lifecycle: the product catalog (every tour, activity, rental SKU with pricing tiers, seasonal rules, resource constraints, add-ons), live availability and capacity (the calendar that every OTA reads from), the customer database (every booker with contact info, marketing consent, repeat-visit history), the booking ledger (every reservation from every channel, direct website, OTA, reseller, walk-up, phone, with status, payment state, and audit trail), the payments and payouts ledger (RezdyPay-processed transactions across 30+ gateways, refunds, chargebacks), the channel-manager distribution graph (which products go to which of the 25,000+ resellers including Viator, GetYourGuide, Klook, Expedia, Google Things to Do, with what markup and fee split), gift cards and promo codes outstanding, guest manifests and check-in records, and the staff/resource schedule.
Founded 2011 in Sydney, Australia by Simon Lenoir and Hugo Sterin.
Developer documentation is fragmented across three separate spec sites (rezdyapi, rezdyconnect, agent) with inconsistent examples and no unified OpenAPI bundle. Rate limits are enforced but the exact per-endpoint quotas and burst behavior are under-documented; integrators discover limits by hitting them in production. Full sourced list under Sources below.
Common alternatives include FareHarbor, Bokun, Checkfront, Peek Pro, TrekkSoft, Xola. Graded alternatives appear under "More from the report card" below.
Grades measure one thing: can a customer's engineering team get their own data out programmatically? We check six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and roll them into a letter grade. Grades get re-verified, and they only move on evidence.
Yes. Supergood maintains an unofficial Rezdy API and MCP server so AI agents and internal tools can read and write Rezdy data. See the Rezdy integration docs at supergood.ai/docs/rezdy-api.