# Your own booking page

Source: https://developers.weerom.com/docs/use-cases/booking-page

> A booking page in your own design on any site, with WeerOm's agenda, rules and mail behind it.

**For** a shop with its own site, or the agency that builds it, that wants booking to look and feel like the rest of the site instead of a link to another page.

The page reads the services and the free times from WeerOm and sends the booking to it. WeerOm checks the shop's rules, puts the booking in the agenda, mails the customer the shop's confirmation with a link to manage the booking, and tells staff. The page needs no database and, with a public key, no server.

| What | You need |
| --- | --- |
| Key | **Public key** A public key in the browser. **Write key** A write key if your server makes the calls. |
| Endpoints | `GET /shop`, `GET /services`, `GET /staff`, `GET /availability`, `POST /bookings`. |

## Steps

1. Read `GET /shop` for the time zone.
2. Let the customer pick a service from `GET /services?active=true`.
3. Show free times from `GET /availability`, for one staff member or for anyone.
4. Ask for name, phone and email, and send `POST /bookings` with an `Idempotency-Key`.
5. On `slot_taken`, ask for the free times again.

```js
const slots = await weerom(`/availability?service_id=${serviceId}&date=2026-11-30&days=7`);

const booking = await weerom("/bookings", {
  body: {
    customer: { email: "lotte@example.com", name: "Lotte Peeters", phone: "+32470123456" },
    service_id: slots.data[0].service_id,
    staff_id: slots.data[0].staff_id,
    starts_at: slots.data[0].starts_at,
  },
  idempotencyKey: crypto.randomUUID(),
});
```

[Build a booking page](https://developers.weerom.com/docs/booking-page) is the full guide: the helper behind `weerom()`, showing times on the shop's clock, every error and what the page shows for it.

## How often

The page asks when a customer looks, so there is nothing to poll. Each visitor costs a few requests: the shop, the services, a week of free times or two, one booking.

## Limits

- **A visitor's limits.** A public key allows 10 booking requests an hour from one address, as on the shop's own form. A page behind a proxy that sends every visitor from one address needs a write key on the server instead.
- **The staff list does not say who does which service.** Take the staff from the free times.
- **No deposit or payment.** WeerOm does not take money, and the API cannot ask for a deposit.
- **One service per booking.** `POST /bookings` takes one `service_id`. The API cannot book two services as one visit.
