Try it without leaving the software you use today
A two-way iCal feed: your system still rules the hours you have already sold and we only publish the empty ones. The day you decide, you switch one of the two off.
20p or 20c per charge · our Club plan, €30/mo
See plans and pricing
The first 2 months of charges, commission-free. The Club plan has a 90-day trial.
Switching software is scary because of what happens on day one
- Migrating everything at once just to find out if it suits you is a blind bet.
- While you test it, somebody has to key the same booking into two places.
- And the first Saturday double booking ends the trial there and then.
Nothing has to be migrated to start: the two systems live side by side.
Your system is the source of truth for what is already taken; we work the hours that stay empty. That is the whole integration you need to try it out.
Look yourself up: your venue is already there
You don’t have to take our word for it. The catalogue is public and your venue may already be listed without you doing anything: open it, look yourself up and check your page. What you see there is exactly what somebody who doesn’t know you yet sees today.
What stops being your problem
The iCal feed, both ways
You paste your system’s .ics address on each court and we stop offering those hours. And we give you an .ics of ours so your system sees our bookings as blocks.
Online booking →It re-reads itself every 15 minutes
With nobody pressing anything, looking 90 days ahead. If the feed has not changed we do not download it whole again, so we never hammer your server.
Even if your feed is private
If your calendar needs an auth header or carries the token in the address itself, you configure it and that is that. That secret is yours and only the venue’s manager sees it.
Public API with a key and a sandbox
Each key is shown once, is revoked whenever you want and is born read-only: write access has to be asked for on purpose. Test keys work against fake data.
Signed webhooks when something happens
Six subscribable events — booking created, confirmed or cancelled, availability changed, payout paid and listing approved — with a signature you can verify and a rotatable key.
If something fails, it is retried and you see it
The queue retries after a minute, five, half an hour, two hours, six and a day. Every delivery is listed with its response, and can be replayed by hand.
A second check before charging
Right before closing a booking we look again to see if your system has just taken that hour. If a clash still slips through, we cancel it and refund in full.
Payments and deposits →The documentation is public
Whoever handles your IT can read the endpoints and the spec before you sign anything, without asking us for access or opening a ticket.
The limits, before you ask
- Reading through the API comes as standard; writing — creating bookings or pushing your busy hours — requires an active Club plan. A key without it gets a clean refusal, not an odd error.
- The iCal feed is re-read every 15 minutes: an hour you have just taken in your system may keep being offered within that window. That is why the live check and the 100 % refund exist.
- The connection to an external booking system is READ-ONLY and uses your credential: you generate it in your provider’s panel and hand it to us. There is no agreement between them and us, so whatever your provider stops allowing stops working.
- Each court has to be paired with its resource in the other system. If it matches neither by id nor by name, we block nothing: we would rather leave an hour open than close one you could have sold.
- Webhooks are delivered at least once: your system has to drop repeats by the event id. After six staggered attempts the delivery is marked failed and waits for you to replay it.
Questions we always get
Do I have to drop my current software?
No. With the iCal feed both live together: yours rules what is already sold and we work the empty slots. If after a few months it is not worth it, you have migrated nothing.
Can I test the API without touching real data?
Yes: there are test keys that only reach a fake-data environment, and live keys that cannot enter it. Neither can do the other’s job, not even by mistake.
What if a key leaks?
You revoke it from the panel and it stops working. The full key is shown only when created: we store its fingerprint, not the key, so nobody can rebuild it.
Will it work with my software, whichever it is?
If it exports a subscribable calendar, yes: that is the lowest common denominator and almost all of them do. If it also has its own API, it can be connected with the credential you generate there.
How it works inside
Who uses it
Which plan includes it
The iCal feed and API reading come with any managed venue; writing comes with the Club plan, whose price and trial are published. And with or without the API, your bookings and members export to CSV whenever you want.
If you are still comparing, start with the plans: the price is published and there is nobody to talk to first. If you have already made up your mind, skip the table: you look your venue up by name, claim it, and pick a plan afterwards. Claiming your page is free.
See plans and pricing