B Bookare Helpbookare.app →

Developers · Guides

Build a booking engine for stays

Direct bookings for rooms, homes, campsites and glamping on the venue’s own website.

1. Show the units

GET /public/units

Each unit: name, kind (room, apartment, home, caravan, glamping, pitch, other), description, guests_up_to, price_per_night_eur (base price), min_nights, bedrooms, bathrooms, size, amenities and photos (image URLs; add ?s=t for a thumbnail).

2. Search dates

GET /public/availability?check_in=2027-07-01&check_out=2027-07-04&guests=2

For every unit taking bookings: available, free (identical units left), why_not (closed, full, too_many_guests, min_nights), nights, total_eur and per_night with each night’s price. Prices include seasons and special nights the venue set. Dates are checked against the venue’s booking horizon; past dates answer 400.

3. Book

POST /public/stay-bookings
{ "unit_id": "…", "check_in": "2027-07-01", "check_out": "2027-07-04", "guests": 2,
  "name": "John Smith", "email": "john@example.com", "phone": "+44 7700 900123", "note": "Arriving late", "consent": true }

201 with code, status (confirmed or requested), total_eur and manage_url. The guest gets a confirmation email with the link to view, pay online (if the venue takes cards) and cancel within the venue’s cancellation window. 409 with a reason means the dates are no longer possible: search again.

Channels

Bookings made through your engine close the nights everywhere: Bookare shares the venue’s availability with Airbnb, Booking.com and other channels it is connected to. You do not need to handle that.