pick between rezdy's agent api and supplier api based on who owns the product inventory
domain: developers.rezdy.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
review the rezdy developer portal landing page, which lists four distinct api surfaces: Agent API, Supplier API, RezdyConnect, and Webhooks
use the Agent API if you are a reseller/OTA that does not own the product — it lets you pull products a supplier has explicitly shared with your account via GET /products/marketplace, check that shared inventory's availability, and push bookings/cancellations back to rezdy
use the Supplier API if you are the tour operator managing your own rezdy inventory — it lets you query and manage your own availability, products, and bookings directly
note a single rezdy account can hold both roles at once (a supplier can also act as an agent reselling other suppliers' shared products), so check which key/role you're authenticating as
if you run your own separate booking system and want rezdy's reseller channels to sell your inventory instead, use RezdyConnect — the inverse integration model where rezdy calls into your system to pull availability/pricing and push bookings, rather than you calling rezdy
Known gotchas
the Agent API only exposes products a given supplier has explicitly agreed to share/distribute to your agent account — you cannot see or book arbitrary rezdy inventory through it
the Agent API and Supplier API are documented as separate specifications under the same developers.rezdy.com portal with separate endpoints/keys, so referencing the wrong spec for your role leads to invalid requests
RezdyConnect is a third, easily confused integration model (rezdy calls your system rather than you calling rezdy's api) meant for suppliers with their own external booking system, not for typical agent/supplier api consumers
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?