B Bookare Helpbookare.app →

AI agents · Agents

Putting booking on the website you build

One line of HTML, a button, or the full API for a custom flow.

get_embed_code returns everything for the venue:

{
  "booking_page": "https://move-studio.bookare.app",
  "button_html": "<a href=\"https://move-studio.bookare.app\" …>Book online</a>",
  "widget": { "timetable": "<script src=\"https://bookare.app/embed.js\" data-venue=\"move-studio\" data-view=\"timetable\" async></script>", "packs": "…" },
  "iframe_fallback": "<iframe src=\"https://move-studio.bookare.app/embed?view=timetable\" …></iframe>"
}

Which to use

  • A “Book online” button in the header and hero: always.
  • The widget on a “Timetable”, “Prices”, “Services” or “Rooms” page: shows live information, resizes itself, and opens booking in a new tab. Views: timetable, packs, services, tables, stays.
  • The REST API if you are building a fully custom experience: developers.

While the venue is a draft, the widget shows the real setup, and booking buttons lead to “booking opens soon”: perfect for the owner to review the site before claiming.

Good practice

  • Use the venue’s real colours in set_branding so the booking pages match the site.
  • Link the booking page from Google Business Profile and Instagram (tell the owner).
  • Do not copy the venue’s prices into static text on the site: the widget always shows the current ones.

More: The booking widget and links.