Skip to content

Public B2B event API

Build event discovery into your own product

Query bookable experiences by city or coordinates, render live dates and prices, then pass customers into checkout with partner attribution preserved.

GET /connect/v1/experiences200 OK
// 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

A focused API for bookable event discovery

01

Location-aware catalogue

Query complete destination catalogues or return distance-ordered experiences around a coordinate.

02

Live booking signals

Fetch date availability, showtimes, ticket options and all-in performance pricing.

03

Attribution included

Every result carries an attributed checkout URL with optional context for touchpoint reporting.

Platform capabilities

Simple to integrate, detailed where it matters

The public partner slug model is designed for client-side use, with predictable errors and a published OpenAPI 3.1 specification.

City and coordinate search
Canonical event category filters
Cursor-based catalogue pagination
BCP-47 localised content
Up to 92-day availability windows
All-in performance and option pricing
Attributed checkout URLs
Clear rate limits and retry guidance
01

Get your partner slug

Create a tickadoo B2B account and copy the public slug from your dashboard.

02

Query the catalogue

Request experiences by destination or coordinates and filter them for your use case.

03

Add availability and checkout

Render bookable dates and deep-link customers with attribution carried through to the order.

Frequently asked

What partners need to know

Does the API require authentication?

No secret key is required. Requests use your public partner slug, which is safe to include in client-side applications.

Is pricing live?

Yes. Availability endpoints return live all-in per-ticket prices and the booking flow validates availability again before payment.

Is there an OpenAPI specification?

Yes. The OpenAPI 3.1 specification is publicly available for code generation, Postman and other development tools.

Next step

Ready to turn travel intent into event revenue?

Read the API docs