Plek API
Build on the booking software your organisation already runs on
Read and change sessions, bookings and customers, embed the booking flow on any website, and get a webhook the moment something happens. One REST API, documented from the same code that serves it.
Three APIs, one host
-
Staff API
Everything staff see and do in the admin app: sessions, series, bookings, customers. API key or staff token.
-
Public booking API
What the booking site and widgets show and book: activities, the agenda, checkout. No authentication.
-
Customer API
A signed-in customer's own account: bookings, participants, passes. Customer token.
Try it with a test key
Staff of an organisation on Plek get a key in one click: sign in to the admin app, pick the organisation and whether the key may change things. It does no more than your own role allows, stops working after an hour, and is kept only in this browser tab. The API reference fills it in for you.
Guides
-
Getting started
Make your first request to the Plek API in five minutes, with a test key or an API key of your organisation.
-
Authentication
API keys for server-to-server integrations, one-hour test keys for trying things out, customer tokens, and OAuth for AI assistants.
-
Conventions
Money, times and timezones, ids, pagination, errors and languages across the Plek API.
-
The booking flow
From the agenda to a confirmed, paid booking with the public booking API, and how the same booking looks from the staff side.
-
Webhooks
Get an HTTPS POST the moment a booking is confirmed, a payment comes in or a session is cancelled, signed so you know it came from Plek.
-
Embedding widgets
Put the booking flow, the agenda or a "Book now" button on any website with two lines of HTML, and react to bookings in the page.
-
The MCP server
Connect Claude, ChatGPT or your own agent to Plek over the Model Context Protocol, with the staff member's own permissions.
-
Rate limits
The request budgets per API key, test key, organisation and MCP connection, the RateLimit headers that show where you stand, and what to do on a 429.
-
Versioning and deprecation
What may change in the Plek API without notice, what never changes without notice, and how long deprecated parts keep working.