Why is 10:00 missing from the booking calendar?

Bookrail's --explain shows why a slot was rejected. Here, Court 1 is already occupied.

Real test output from our open-source booking API. Try it: bookrail.dev/docs/quickst...

Two padel courts, opening hours, a confirmed booking. Here's the whole flow with Bookrail's CLI: configure the club, check availability, book a slot.

Open-source booking API. Real output, test environment.
Try it: bookrail.dev/docs/quickst...

Bookrail is an open-source booking API: availability, holds, bookings and webhooks. TypeScript SDK, CLI and MCP included. Apache 2.0, early access.

Get a test key: bookrail.dev/signup
Code: github.com/bookrail-dev...

Bookrail is public today. The engine under your booking product: availability, holds, bookings, policies and webhooks.

TypeScript, PostgreSQL, Apache 2.0. You build the interface; the engine handles capacity.

github.com/bookrail-dev...

The countdown hits zero, but the customer still has the tab open.

Bookrail rejects that expired hold with 409 hold_expired. The app needs to check availability again.

Real API output from our test environment. We’re preparing the open source release.

Two requests arrive together. Only one slot is available.

This Bookrail demo shows real API responses from our test environment: one booking confirmed, one rejected with 409 slot_unavailable.

Capacity is enforced in Postgres.

How do you test double bookings?

Booking software gets interesting when two people want the same slot, a hold expires, or the clocks change.

We're building Bookrail to handle that layer for developers, and sharing what we learn.

Open source release coming soon.

What booking edge case caught you out?

bookrail.dev