Version 1

The WeerOm API

Read a shop's bookings, customers, services, staff and payments, take bookings through the shop's own rules and mail, and get a webhook the moment a booking or a payment changes. Send the key the shop made in its admin, and every endpoint answers JSON.

Base URLhttps://api.weerom.com/v1

GET/v1/payments?limit=1
curl https://api.weerom.com/v1/payments?limit=1 \
  -H "Authorization: Bearer $WEEROM_KEY"
200 OKapplication/json
{
  "object": "list",
  "data": [
    {
      "object": "payment",
      "id": "0b6f2a4e-5d1c-4f7a-9a3e-2c8d1e6f4b90",
      "booking_code": "UEAMEFC9",
      "paid_at": "2026-11-21T10:12:40.000Z",
      "description": "Knippen en baard",
      "amount_cents": 4000,
      "net_cents": 3306,
      "vat_cents": 694,
      "vat_percent": 21,
      "currency": "EUR",
      "method": "bancontact",
      "customer": { "name": "Lotte Peeters", "email": "[email protected]" }
    }
  ],
  "has_more": true,
  "next_cursor": "WzE3OTUyODcxMzA0MTIsIjBiNmYy..."
}
Requests a minute for each key
120
Objects on one page, at most
100
Money in whole cents, VAT included
4000 = €40
Every time, in ISO 8601
UTC

Guides

Eight guides, from a first request to a booking page of your own and webhooks.

Use cases

Ten things people build on the API. Each names the key it needs, the steps, a code sketch and what the API cannot do for it.

Endpoints

Every endpoint works on the shop the key belongs to. Each page has a playground that takes your key.