Slotr Docs

Slotr lets anyone take bookings from a link — and lets you build on the same engine. Sync your own entities in, let Slotr index and enrich them with AI, then search, quote and book over that index. These docs cover every way you build on it: a React UI, the HTTP API, and tools for AI agents.

How Slotr worksCopy Anchor Link

You sync your own domain objects — listings, doctors, courts, rooms — into Slotr as bookables, keyed by your id. Your database stays the source of truth; Slotr keeps an indexed copy.

From there Slotr gets to know your entities. It enriches the index offline with AI — learning your domain, filling in what attributes mean and sharpening how things relate — so search matches what a customer actually wants, not just literal filters. It gets better the more you sync.

1. Index your entities as bookables — in bulk for the first sync, or one at a time.
2. Search the index by attribute filters to find what fits a request.
3. Book — turn a bookable into a confirmed booking with the Booking Kit.

Build on the APICopy Anchor Link

Every operation is generated from the OpenAPI contract — the same contract the SDKs and server types are built from, so the docs never drift.

Sync one bookable, then search for it:

PUT /v1/bookables/court/padel-01
Authorization: Bearer <your-token>
Content-Type: application/json

{ "name": "Padel Court 1", "attributes": { "surface": "glass", "indoor": true } }

POST /v1/search
Authorization: Bearer <your-token>
Content-Type: application/json

{ "type": "court", "filters": { "indoor": true } }

Base URL is https://api.slotr.dev. Every endpoint except health takes a JWT that scopes requests to your project — you only ever see and write your own bookables.

Take bookings in ReactCopy Anchor Link

The Booking Kit (@slotr/react) is the booking UI: a themeable calendar, an out-of-the-box modal, and headless hooks when you want to bring your own UI.

import { BookingCalendar } from "@slotr/react/booking-calendar";
import "@slotr/react/styles.css";

<BookingCalendar id={bookingId} />

Which do I need?Copy Anchor Link

• Taking bookings in a React UI? Use the Booking Kit — one component, themeable, with an out-of-the-box modal.
• Building a backend integration? Use the API.
• Wiring up an AI agent? Point it at the MCP server — same capabilities as the API, as tools.

Built for agentsCopy Anchor Link

Every page here is readable as plain Markdown — append .md to any URL — and listed in /llms.txt for agents.