Location-aware catalogue
Query complete destination catalogues or return distance-ordered experiences around a coordinate.
Public B2B event API
Query bookable experiences by city or coordinates, render live dates and prices, then pass customers into checkout with partner attribution preserved.
// Live event inventory for your product
fetch("/connect/v1/experiences?city=london")
{
"title": "Hamilton",
"fromPrice": 75.24,
"currency": "GBP",
"checkoutUrl": "https://tickadoo.page/..."
} 1,000
Requests per minute
18,000+
Bookable experiences
1,400+
Cities worldwide
OpenAPI
Machine-readable spec
Why it works
Query complete destination catalogues or return distance-ordered experiences around a coordinate.
Fetch date availability, showtimes, ticket options and all-in performance pricing.
Every result carries an attributed checkout URL with optional context for touchpoint reporting.
Platform capabilities
The public partner slug model is designed for client-side use, with predictable errors and a published OpenAPI 3.1 specification.
Create a tickadoo B2B account and copy the public slug from your dashboard.
Request experiences by destination or coordinates and filter them for your use case.
Render bookable dates and deep-link customers with attribution carried through to the order.
Frequently asked
No secret key is required. Requests use your public partner slug, which is safe to include in client-side applications.
Yes. Availability endpoints return live all-in per-ticket prices and the booking flow validates availability again before payment.
Yes. The OpenAPI 3.1 specification is publicly available for code generation, Postman and other development tools.
Next step