How to Get Your Rezdy API Key (and What to Build With It)

How Rezdy API access works

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.

What the Rezdy API lets you do

The Rezdy API gives you programmatic access to the core data in your account. Broadly that covers:

• Products, sessions and availability
• Bookings, customers and participants
• Pricing options and extras
• Vouchers and gift cards
• Agents, resellers and commissions

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.

Rezdy and no-code tools

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.

Building with the Rezdy API

Connecting Rezdy to another system means working through five things, in roughly this order:

1. Authenticate using the credentials above, and store them somewhere your team can rotate
2. Map the data, deciding what moves between Rezdy and the other system, in which direction, and triggered by what
3. Handle the edge cases, such as a record that already exists on one side but not the other, or a partially completed transaction
4. Build error handling, so a failed call is retried or surfaced rather than silently dropped
5. Set up monitoring, so you find out something stopped working before it becomes an accounting problem

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.

When to bring in a developer

Some Rezdy API work is genuinely straightforward. Some is not. An honest split:

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.