Connect once
You provide a Rezdy API key from your account. Bookings, changes, and cancellations flow to your add-ons automatically from then on.
API + Webhooks
Noosa · Australia · NZ
Rezdy API Integration
Rezdy developer for tour and activity operators
Local Stack is an independent Rezdy developer based in Noosa, building add-ons and integrations on the official Rezdy API for tour, charter and transport operators across Australia and New Zealand. Rezdy keeps taking the bookings. We build the manifests, allocations, emails and booking websites around it.
How It Works
Rezdy API integration, beside your account
Each service connects to your existing Rezdy account through the official API and webhooks. Rezdy stays your booking system. The add-ons see every booking, change, and cancellation within seconds and handle the jobs Rezdy doesn't.
Nothing changes in Rezdy
Your products, prices, agents, and channels stay exactly as they are. Add-ons work beside the platform, not inside it.
Zero Disruption
Pick only what you need
Each service is an independent module. Start with the one that hurts most; add or drop others as the business changes.
Per-Module
Services
What we build on the Rezdy API
Built for tour, charter, and transport operators. Every module runs on live booking data from your own account.
Contractor and operator manifests
A standalone daily manifest on the Rezdy API with per-login product access and live check-in status, so contractors see their passengers and your calendar stays internal.
In Production
Seat and vehicle allocation
Assign customers to specific seats, buses, or boats with sticky allocations and a printable run sheet. Rezdy sells the tickets; the allocator manages the physical fleet.
Buses · Boats
Branded confirmations
Your own confirmation and pre-arrival emails per product, sent from the booking webhook with each customer's details.
Per-Product
A whole booking website on Rezdy
Catalogue, live availability, card checkout and confirmations on your own domain, with Rezdy underneath as the booking system.
Your Domain
Case Study · Rezdy Manifests
Contractor manifests for a national-park shuttle operator
A car-park and shuttle operator at one of New Zealand's busiest day walks sells through Rezdy, with several shuttle contractors carrying the passengers.
The problem
Each contractor needed the day's passenger list, but the only way to see it was a login to the operator's entire Rezdy calendar.
Problem
What was built
A standalone manifest app on the Rezdy API with per-login product access, live check-in status and a rolling 90-day sync.
Built
The result
Contractors see only their own manifest, and the Rezdy calendar goes back to being internal. In daily use since October 2026.
Result
See It Running
A complete booking website built on the Rezdy API
A demo site of our own, on its own domain: catalogue, product pages, live availability, card checkout and branded confirmation emails, with Rezdy as the booking system behind it all.
Questions
Rezdy integration questions
The things operators usually ask on the first call.
Are you part of Rezdy?
No. Local Stack is an independent developer. Everything is built on Rezdy's public API, using access from your own account.
Independent
What do I need from my Rezdy account?
API access for your account. We walk you through getting a key, and check on the scoping call what your plan exposes before quoting anything.
API Access
Will it see agent and OTA bookings?
Yes. Bookings from your website, agents and online channels all land in Rezdy as orders, and the add-ons read them from there.
Every Channel
Does anything change in how we sell?
No. Your products, prices, agents and channels stay as they are. If Rezdy updates its API, the add-on is updated as part of ongoing support.
Zero Disruption
Do you work outside the Sunshine Coast?
Yes. Rezdy work is done remotely for operators across Australia and New Zealand. The manifest app above runs for an operator in New Zealand.
Remote
Getting Started
How an engagement runs
A short scoping call, then a fixed quote per module. Most modules connect to a live account in days, not months. Waitlists, pre-filled paperwork, weather holds and operator reporting are also possible on the same foundation.
Scope
A call to pin down the gap, and a check of what data your Rezdy account and plan expose.
Step 1
Build and connect
The module is built and tested against a copy of your data before it touches your live account.
Step 2
Run
Hosted, monitored, and supported by Local Stack, billed as a monthly service you can cancel.
Step 3