Boozie for developers
The Boozie API lets venues and the apps they use read their tables, sessions, bookings, guest list and reviews, make and confirm bookings, and get changes pushed by webhook. It is a JSON REST API with an OpenAPI 3.1 spec.
Get a sandbox key
Try the API on the sandbox, a made-up venue with fake guests and bookings. Enter your email and we’ll send you a test key.
Guides
- QuickstartGet a sandbox key, read your venue and create your first booking in five minutes.
- AuthenticationAPI keys, scopes and plans, test and live keys, and rolling a key without downtime.
- OAuth appsBuild an app many venues install: authorization code with PKCE, tokens and refresh.
- OrganisationsOne key for a group of venues: org keys, choosing the venue and listing what a key covers.
- WebhooksGet bookings and guest-list changes pushed to you, signed, retried and replayable.
- ConventionsTimes, money, paging, enums, idempotency and rate limits: the rules every endpoint follows.
- ErrorsProblem details (RFC 9457) and every error code the API returns.
- SandboxThe sandbox venue, its test data and how it resets every night.
- ChangelogWhat changed in v1, and how we change the API without breaking you.
The basics
- Sandbox
https://api-dev-799b.up.railway.app/public/v1- Production
- Announced when it opens.
- Auth
Authorization: Bearer bz_test_…: a venue key, an organisation key or an OAuth token.- Spec
- OpenAPI 3.1 (JSON)
- Need access to a real venue?
- A venue owner makes a key in the Boozie back office. To build an app for many venues, contact us to register an OAuth app.