Getting started

Kwickblocks runs one deployment per venue group. Each deployment has a Booking API (REST, JSON) and an MCP server that offers the same operations as tools for AI agents. Both use the same integration key.

Surface	Base URL
Booking API	https://<tenant>.kwickbooking.com/public/v1
MCP server	https://<tenant>.kwickbooking.com/mcp
Live reference for the deployment	https://<tenant>.kwickbooking.com/public/v1/docs

Your base URL

kwickbooking.com in every example on this site is a placeholder root. The venue’s admin gives you your base URL together with your key, and it may be the venue group’s own domain. Replace https://<tenant>.kwickbooking.com with that base URL in every example here, including the live reference at <your base URL>/public/v1/docs.

Keys

Send your integration key as a Bearer token on every request:

Authorization: Bearer kb_ik_sandbox_…

There is no public sign-up: keys come from the venue’s admin. See Integration keys for capabilities, venue scope, sandbox keys and rotation.

A first call

List the venues your key can use:

curl -H "Authorization: Bearer kb_ik_sandbox_…" \
  https://<tenant>.kwickbooking.com/public/v1/venues

Use a venue’s id wherever an operation takes venueId. A key that covers one venue doesn’t need to send it.

Formats

• Dates are venue-local yyyy-MM-dd and times are venue-local HH:mm, in the venue’s own time zone.
• Money is in pence (amountPence), with a display string such as £25.00 alongside.
• Every write is a POST with an Idempotency-Key header, so a retry never books twice.

The summary field

Every successful answer has a summary: one plain-English sentence, in UK formats, that an agent can read to a guest as it is. For example, “Booked: Fri 16/10 at 20:00 for 4. Reference 4827 1936.”

Errors

Errors are RFC 9457 problem details (application/problem+json). The detail is written so it can be read to a guest, and type links to a page here that explains the problem.