Developers · Guides
Integrations: CRM, reports and automation
Use an API key to connect Bookare to the rest of a venue’s tools.
With an API key, your server can read and change everything an admin can. Some patterns:
Members to a CRM or newsletter tool
GET /admin/members?offset=0 50 per page; "total" says how many
GET /admin/members?status=active&search=…
GET /admin/members/{member_id} packs, upcoming bookings, recent history, totals
wants_news tells you who agreed to receive offers. Keep that consent in your tool: only email those who agreed.
New sign-ups from your own forms: POST /admin/members { "name", "email", "phone", "activate": true }.
Daily report
Every morning, with a read-only key:
GET /admin/classes?from=2026-12-01&to=2026-12-01 how full each class is (today’s date)
GET /admin/unpaid who owes what
GET /admin/sales?from=2026-12-01&to=2026-12-31
Accounting export
GET /admin/sales?from&to gives totals by payment method and by pack. Per member, GET /admin/members/{id} lists their packs
with prices and payment dates.
Keeping a timetable in sync
GET /admin/timetable the weekly classes
POST /admin/timetable add one
PATCH /admin/timetable/{weekly_class_id} change it (dates already booked keep their time)
DELETE /admin/timetable/{weekly_class_id}
Stays: prices from a revenue tool
PUT /admin/nightly-prices { "unit_id", "from", "to", "price_per_night_eur", "weekdays" }
POST /admin/nightly-prices/reset
POST /admin/seasons / DELETE /admin/seasons/{season_id}
POST /admin/closed-days / POST /admin/closed-days/open
Watching for changes
There are no webhooks. Poll gently (for example every few minutes) the lists you care about:
GET /admin/classes, GET /admin/stay-bookings?from&to, GET /admin/unpaid, and compare with what you stored.
Things the API leaves out on purpose
Health answers of members; changing a member’s email or deleting a member; team, roles, payment provider settings, plan and billing, the domain, and API keys. Those stay in the admin.