Docs · getting started in 15 minutes

From zero to a booked meeting,
in seven sections.

Stub content for v1. Each section will grow into a full reference page as the product ships. The order below is also the order to do it in.

01 / 7

Connect your calendar

Slotsy supports two paths. Use whichever your stack prefers; you can switch later without losing data.

DRAFT Full reference expands here pre-launch · target ~600 words + screenshots + code samples per section.

02 / 7

Brand your booking page

Logo, primary colour, custom CSS, sender domain. Server-rendered into the head — your page renders before the stylesheet loads.

DRAFT Full reference expands here pre-launch · target ~600 words + screenshots + code samples per section.

03 / 7

Set up event types

Each event type has its own duration, price, intake form, buffer, and availability window. Members pick by name.

DRAFT Full reference expands here pre-launch · target ~600 words + screenshots + code samples per section.

04 / 7

Share the booking link

Three ways: custom domain (book.your-brand.com), Slotsy URL (slotsy.net/u/yourname), or one-script embed on your own site.

DRAFT Full reference expands here pre-launch · target ~600 words + screenshots + code samples per section.

05 / 7

Embed the widget

A single <script> tag drops the booking widget into any site. Under 12 KB gzipped, inherits your typography.

DRAFT Full reference expands here pre-launch · target ~600 words + screenshots + code samples per section.

06 / 7

Accept payments (BYO Stripe)

Paste a restricted Stripe API key. Member payments go directly to your account; we never sit in the path.

DRAFT Full reference expands here pre-launch · target ~600 words + screenshots + code samples per section.

07 / 7

Receive webhook events

JSON POST on every booking event with an HMAC-SHA256 signature header. Retry on 5xx with exponential backoff.

DRAFT Full reference expands here pre-launch · target ~600 words + screenshots + code samples per section.