How to Get Your Rezdy API Key (and What to Build With It)
How Rezdy API access works, what the Rezdy API lets you connect, and when you need a developer to do it properly. Perth, Melbourne, Sydney and Brisbane.
How Rezdy API access works, what the Rezdy API lets you connect, and when you need a developer to do it properly. Perth, Melbourne, Sydney and Brisbane.
Who this is for
Tour, activity and experience operators who want to connect Rezdy to other systems and need to understand how its API works before committing to anything.
Question this answers
How do I get Rezdy API access and what can I actually connect Rezdy to?
What you will leave with
Rezdy uses an API key issued from your Rezdy account, sent with each request. The exact screens move around as Rezdy updates its interface, so rather than repeat a menu path that may already be out of date, the reliable source is the official documentation: Rezdy API documentation.
Rezdy distinguishes between supplier and agent API access. Which one you hold determines what the key can see, and it is a common source of confusion.
Treat API credentials like a password. Anyone holding them can read and often write data in your Rezdy account. Do not paste them into untrusted tools, and do not send them over email or chat.
The Rezdy API gives you programmatic access to the core data in your account. Broadly that covers:
With that access you can push data into accounting or reporting systems, keep records in step across tools, and build dashboards from live Rezdy data rather than from exports someone has to remember to run.
Zapier support for Rezdy is limited. Zapier coverage is limited, so most Rezdy integrations use the API directly. That is why searches for connecting Rezdy through no-code tools tend to turn up workarounds rather than a clean answer.
Connecting Rezdy to another system means working through five things, in roughly this order:
A common pairing is Rezdy with Xero or MYOB. Read-only reporting is usually straightforward. Live two-way sync is where the mapping and error handling turn it into a proper development project.
Some Rezdy API work is genuinely straightforward. Some is not. An honest split:
Deposits, balances and agent commissions all need separating before anything reconciles.
Selling the same seat twice is the failure mode when availability is not single-sourced.
Net versus gross treatment changes both the invoice and the revenue figure.
Partial refunds and credits are where booking-to-ledger integrations usually break.
These integrations look simple from the outside. The work is in the detail: field mapping, conflict resolution, error recovery, and keeping everything in step as both Rezdy and the connected system change over time.
If the integration touches invoicing, stock or payroll, getting it wrong has real financial consequences. A properly built integration with monitoring and alerting is worth the upfront cost.
A Rezdy application programming interface (API) key is issued from your Rezdy account and sent with each request. The screens move as Rezdy updates its interface, so the official Rezdy API documentation is the reliable source for the current steps. Rezdy also separates supplier and agent API access, and which one the account holds determines what the key can see, which is a common source of confusion.
No. Treat Rezdy application programming interface (API) credentials like a password, because anyone holding them can read and often write data in the Rezdy account. Do not send them over email or chat, and do not paste them into untrusted tools. An integration should keep the key somewhere the team can rotate it.
The Rezdy application programming interface (API) covers products, sessions and availability; bookings, customers and participants; pricing options and extras; vouchers and gift cards; and agents, resellers and commissions. With that access, booking data can be pushed into accounting or reporting systems, kept in step across tools, and used in dashboards built from live Rezdy data rather than exports someone has to remember to run.
Only in a limited way. Zapier coverage for Rezdy is limited, so most Rezdy integrations use the application programming interface (API) directly, and searches for no-code options tend to turn up workarounds rather than a clean answer. Even where a no-code chain works, there is rarely a way to see what failed when it breaks or to replay the records that were missed.
Bookings into accounting, availability across channels, agent commissions and cancellations are the hard parts. Deposits, balances and agent commissions need separating before anything reconciles, and if availability is not single-sourced the same seat can be sold twice. Partial refunds and credits are where booking-to-ledger integrations usually break. These integrations look simple from the outside, but the real work is in field mapping, conflict resolution and error recovery.
Ask the author
Ask it here and it comes straight to Kasun, who wrote this. No sales call, no obligation, and a real answer even if the answer is that you do not need us.
Kasun Wijayamanna
Founder, replies within one business day
Tell us what you are comparing, replacing, or trying to improve. We will come back with a practical recommendation and realistic scope.
Built here. Your data stays here.
Thanks for reaching out. We will get back to you within one business day.
See what else we do