The API Report CardAPI Index
THE API REPORT CARD / Hospitality & Travel / Bokun
Bokun

Bokun API

Tours & Activities Reservation System / Channel Manager for Experience Operators · bokun.io

Bokun publicly documents three API products: REST booking APIs (v1 and v2), a Channel Manager API, and GraphQL, with OpenAPI specs on GitHub and OAuth 2.0 for apps. Access is self-serve with a Bokun account. The 400 req/min limit is shared per vendor across all API keys.

Last verified: July 2026Hospitality & Travel
API GRADE
A
VERIFIED JUL 2026

SCORECARD

ExistenceGOODThree documented surfaces at bokun.dev: REST v1 and v2 booking APIs, a Channel Manager API, and GraphQL.
AccessGOODOpen to any vendor or developer with a Bokun account; apps created in the Partner Dashboard get a key and secret.
CoverageGOODReservations, products, availability, customers, and pricing, plus reseller distribution via the Channel Manager API.
AuthGOODOAuth 2.0 authorization-code grant for apps; API key and secret signing for direct REST calls.
Docs & DXGOODPublic docs, sandbox, and OpenAPI YAML specs on GitHub; webhook replay behavior is sparsely documented.
StabilityGOODThrottling is documented: 400 req/min per vendor with Retry-After, and reservation calls are exempt from limits.
MORE FROM THE REPORT CARD
RezdyCPeek ProD+CheckfrontCTrekkSoftC
Supergood: Bokun shipped a real API. Most vendors don't; we ship near-native APIs for the rest.

Frequently asked questions

Bokun scores A on the API Report Card. Bokun publicly documents three API products: REST booking APIs (v1 and v2), a Channel Manager API, and GraphQL, with OpenAPI specs on GitHub and OAuth 2.0 for apps. Access is self-serve with a Bokun account. The 400 req/min limit is shared per vendor across all API keys.

Tried to integrate with Bokun?
SOURCES
Bokun-to-Viator API connection drops and the system does not honor closeout placements pushed via API, resulting in bookings landing on closed time slots trustpilot.com ↗
Two parallel REST API versions (v1 and RESTful v2) plus a GraphQL endpoint create integration confusion; some endpoints exist on one surface only, forcing partial migrations bokun.dev ↗
400 req/min per-vendor rate limit is shared across all API keys for the same vendor, so an operator with multiple integrations (POS, accounting, channel manager) can collide on the same ceiling without warning bokun.dev ↗
Webhook delivery and replay behavior is sparsely documented; integrators report needing to build their own polling fallback to catch missed booking events capterra.com ↗
Channel-manager plugin authors must choose between two-step (reserve + confirm) and single-step booking flows; mismatched choices against operator configuration cause silent inventory drift bokun.dev ↗
Operators report that third-party integrations (accounting, CRM, marketing) frequently break after Bokun platform updates, with no public changelog or deprecation policy for API consumers trustpilot.com ↗
Partner Dashboard / app-creation flow requires Bokun account approval; sandbox is functional but documentation gaps around test-mode behavior force trial-and-error against production data bokun.dev ↗
Customer service uses bot-style form-letter responses on difficult issues, schedules calls then no-shows, and asks customers to suggest alternative times rather than resolving the underlying problem trustpilot.com ↗
Availability/inventory sync between Bokun and connected channels (especially Viator) is unreliable, fixing one issue breaks another, with sync problems persisting for weeks while products become unbookable trustpilot.com ↗
Viator time slots appear as unavailable on Viator when they are in fact open in Bokun, leading to lost direct bookings; troubleshooting can drag on for a month or more trustpilot.com ↗
Reports of double bookings caused by Bokun-to-Viator API connection failures that customer service confirms as resolved but operators continue to experience trustpilot.com ↗
System has been criticized as incapable of reliably blocking time slots once already booked, described by operators as defeating the entire purpose of a reservation system trustpilot.com ↗
Per-booking fee structure layered on top of monthly subscription makes total cost-of-ownership hard to predict; operators report not knowing real cost until several months on the platform hamzaliaqat.com ↗
Mixed Capterra/Software Advice reviews note steep learning curve, dated UI in places, and that resolving complex configuration issues requires deep platform expertise most small operators lack capterra.com ↗
Tripadvisor ownership creates a perceived conflict of interest: Viator (sister product) gets preferential 0% Bokun fees, which some operators view as steering distribution toward the parent company's marketplace at the expense of OTA neutrality medium.com ↗
© Supergood Systems, Inc.