Skip to content
Ecosystem

Your booking data is yours to use

An API and webhooks for whoever builds it, and pixel, CAPI and UTM parameters on the booking flow for whoever runs your marketing.

Developers and Measurement. API and webhooks for whoever builds it, pixel, CAPI and UTM parameters for whoever runs your marketing

01

Not locked in a monthly export

Bookings, customers, spend and membership status come through the API as they happen, rather than at month end.

02

It talks to what you already run

Webhooks push every booking out to your CRM or your reporting the moment it lands, and let those systems start something back here.

03

Know which ad produced the booking

Pixel, CAPI and UTM parameters run on the booking flow, so a campaign is judged on bookings taken rather than clicks counted.

04

Your agency stops asking you for numbers

Whoever runs your marketing works from live booking data instead of a spreadsheet you put together on a Sunday.

05

Ask your own venue a question

Connect an AI assistant to a venue and it reads and acts on that data, with the same permissions a member of your team would have.

06

Your web developer will be fine

Booking goes onto the site you already have, measurement intact. Point them at us and we will take it from there.

07

The documentation is there when you want it

Full API reference, webhooks and authentication, written for whoever builds it. Most operators never open it, and nothing here needs a developer to get started.

FAQ

Frequently asked questions

Yes. A per-venue JSON API with an OpenAPI document, inbound and outbound webhooks, signed requests, and OAuth.

Yes, one per venue.

Yes. Pixel, Conversions API and campaign parameters run on the booking flow, so a booking can be tied to what produced it.

See the platform built for your operation

30-minute demo. Configured to your venue's layout, staffing model, and existing hardware.