Steps

understand that bokun's Channel Manager connects a bokun product to an external system that acts as the master source of truth for availability/bookings, and is supported only for Experiences-type products
choose a transport for your plugin: gRPC (original, lower latency) or REST (added May 2019, full functional parity with gRPC) per the Channel Manager API docs
design and build a custom plugin implementing the required lifecycle: plugin registration, retrieval of plugin definition, plugin configuration, product mapping, shallow & deep availability searches, reservation/booking, cancellation, and booking amendment
work with bokun's API team to test the plugin end-to-end before it goes live — this is a supported development process, not a self-serve toggle
once live, bokun performs availability checks against the plugin before allowing a booking, then pushes confirmed bookings through to the external system
once connected, the product becomes sellable to bokun's marketplace of resellers and global OTAs without separate per-channel integration work

Known gotchas

this is not a self-serve API-key integration: it requires building and testing a custom plugin with support from bokun's API team before the connection is usable
channel manager only supports Experiences-type products — other product types are not eligible
bokun also documents a separate OCTO API as an alternative standardized connectivity option, which may fit some integrations better than a custom channel manager plugin

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

connect a supplier's external inventory system to bokun's channel manager for resale on ota marketplaces

Steps

Known gotchas

Give your agent this knowledge — and 15,500+ more routes

Need this verified for your stack — or a route we don't have yet?