All chapters

Embedding the widget

With the reservation widget, guests book directly on your own website — no detour through portals and no commission. Embedding it is a one-time copy-and-paste step and takes about five minutes.

Copy the embed code

  1. In the backoffice, open Settings → Widget.
  2. Copy the HTML code shown (a <script> snippet).
  3. Paste it wherever you want on your website — for example on a dedicated "Reserve" page. In site builders such as WordPress, Wix or Jimdo, use the HTML/embed block for this.

The color in the configurator is pre-filled with your brand color from Settings → Appearance (see Brand color). You can override it here at any time — the embed code always writes the chosen color as data-color. A snippet that is already live on your website therefore does not change when you set a different brand color later: copy the code again in that case.

Above the code of every widget there is the tick box Add the line, each with the widget's own text: “Reservations with VidiReserve”, “Booking with VidiReserve” (events), “Vouchers with VidiReserve” and “Request with VidiReserve” (group request). It is off. If you tick it, the code adds a small line with a link to vidireserve.com below the widget — in the language you chose for the widget. Without the tick the code contains no such line; the line is optional and changes nothing about the widget. The tick is not saved: it applies to the code you are copying right now.

Widget size

How large your widgets appear on your website is set for all of them at once under Settings → Appearance: Small, Normal or Large. Text, spacing, cards and buttons grow or shrink together. The default also applies to widgets that are already embedded — you do not need to touch your website. It can take a few minutes until the change shows there.

If one widget should differ, choose its size in the configurator: buttons freely in percent (50 to 200 %), cards, grids, lists and the calendar in the same three steps. The embed code then carries the size as data-size, for example data-size="l" or data-size="130"; without that line the default from Appearance applies. The window that opens after a click, the “Full page” form and the embedded request form keep their size.

Your widgets appear in our design on every website: your website's own CSS (fonts, colors, borders) no longer reaches into the widgets. You adapt them through the color and the size.

Whitelist your domain

The domain allow list decides which websites your widget may run on. As long as the list is empty there is no restriction: the widget runs on any page where someone pastes the code. To lock it down, we recommend entering your website address in the backoffice under Widget → Security (for example www.my-restaurant.com) — the widget then only runs there and shows an error message everywhere else.

Enter the address exactly as it appears in the browser: my-restaurant.com and www.my-restaurant.com are two separate entries. *.my-restaurant.com approves the main domain and all subdomains at once. The allow list applies to every widget — reservations, events, vouchers and group requests.

Spam protection

The widget ships with multi-layer protection against automated bookings (including an invisible bot check). You do not need to configure anything — real guests never notice it.

Widget activity

Under Widget › Activity you see every submission of the last few days with its result (success received, validation input incomplete, spam or honeypot suspected bot, rate_limit limit reached) and, in the Widget column, where it came from: reservation, event, group request, contact form, voucher, waiting list and offer page. Waiting lists and the offer page also appear when the guest booked directly on VidiReserve instead of in your widget — so you can see in one place whether bots are targeting your forms.

Tip: link the "Reserve" button on your website directly to the page with the widget — the fewer clicks it takes to reach the form, the more bookings you receive.

Your own button on your website

Do you already have your own "Reserve" button or link on your website, for example in the menu or the header? Then that very button can open the reservation window. Add the line data-trigger to your embed code and enter how the widget recognises your button: a CSS selector, for example [data-reserve-table] or .book-now. A click on it opens the same as our button.

<script src="…/widget/v2.js?v=…"
        data-restaurant="your-business"
        data-trigger="[data-reserve-table]"></script>

<a href="/reservation" data-reserve-table>Book a table</a>

All other lines of your embed code stay as they are. The widget button itself may stay hidden: a container with display:none around the embed code is fine, the window still opens. Your link keeps its target — without JavaScript it still leads to your reservation page.

Only one snippet per selector on a page: if two embed codes react to the same selector, both open their window. There is no field for data-trigger in the configurator — your web designer adds the line by hand.

Accessible version

Below the widget there is a small "Accessible version" link. It opens the same booking form as a standalone page in a new window — without the embedded frame.

Guests using a screen reader or keyboard can complete their booking that way even if the embedded frame gives them trouble. There is nothing to set up; the link is there automatically.

The calendar variant is fully keyboard-operable as well: the arrow keys move between days, Page Up and Page Down switch months, Home and End jump to the start and end of a week, and Enter picks the day. Fully booked and past days are skipped.

When you pick your brand color in the configurator, the contrast against white is shown right below the color field (for example "Contrast with white: 3.8:1"). Below 4.5:1 the widget automatically switches text on colored areas to a dark tone and uses a slightly darker variant for text in your color — your brand stays recognisable and the text stays readable.

Embed one specific event

Instead of all upcoming dates you can show exactly one event on your page — for example on the subpage that is about that one course anyway. In the widget configurator, pick “One specific event” at the top, then the date and one of three forms:

  • Card (data-variant="single") — a wide card with image, date, price, spots left, an excerpt of the description and a booking button. If the description is longer, “show more” expands it in full right inside the card.
  • Button only (data-variant="button") — just the button. It opens the same booking window as the card. With data-label="Reserve a spot" you give it your own wording; without that line it reads “Book now”.
  • Full page (data-variant="page") — the event's detail page appears right inside your page: image, gallery, date, location, price, description and cancellation terms, with the booking button below. Without our navigation, without a cookie banner, in your brand color.

The event itself appears in the embed code as data-event="…". If it is sold out, past or paused, the widget stays and says so — the button is then not clickable.

If the date is deleted or not yet published, it depends on the form you picked: with Card and Button only nothing is shown at all and your page stays intact. With Full page the frame shows a short notice instead — the frame itself stays visible, because it carries the page rather than waiting for data.

The domain allowlist applies to the embedded page as well: without your address on the list the frame shows an error message.

Existing embeds are unaffected: without the data-event line everything stays as it is. For the new form to reach your website, copy the code once more and replace it.

Embed offers with date picker

For offers with date picker, where your guests pick the date themselves (for example a kids’ birthday party or a farm tour), there is a widget of its own: Widget → Offers Widget. Choose “All offers” — cards with image, duration and “from” price — or “One offer” as a single “Choose a date” button. A click opens the calendar with the free start times in a window; after that comes the familiar booking form with packages.

<div id="vr-offers"></div>
<script src="…/widget/offers-v2.js?v=…"
        data-restaurant="your-business"
        data-offer="kids-birthday"
        data-variant="button"
        data-color="#c0392b"
        data-lang="en"
        data-container="vr-offers"></script>

Without data-offer the widget shows all active offers (at most data-max, default 6). An inactive offer or one without an active package does not appear. The same domain whitelist and spam check apply as for events.

Vouchers: window or new tab

For the voucher widget you decide in the configurator where the purchase happens:

  • Window (data-mode="modal") — the purchase opens in a window on top of your page, exactly like the events widget. Your visitors stay on your website.
  • New tab (data-mode="redirect") — the checkout page opens in a new tab. This used to be the only option and stays in place for every existing embed.

Payment in the widget. After submitting, the window shows the confirmation. The pay button opens our payment page in its own window — there your customers can see the address bar, as the payment providers require. Your page and the widget stay where they are: the widget shows “Payment is in progress in the new window …” and, as soon as the payment has gone through, the confirmation with the link to the invoice. The same applies to prepayment when booking an event. If someone has closed the window, they open it again with “Reopen payment window”; if the browser blocks the window, the widget offers a direct link to the payment page. If the payment window is still open, the same button only brings it to the front without restarting a payment in progress. If the order or booking is cancelled in the meantime, the widget shows “Nothing left to pay” without a pay button. Payment is also possible at any time later via the link in the email.

Countdown with immediate payment. If the event has Place only with immediate payment, the confirmation in the widget shows above the pay button how long the place is still held (“Please pay within 14:32 min, otherwise the place will be released”). One minute before the end a screen reader announces it. When the time runs out, the button disappears and the widget offers Book again in a new window. Once your customer starts paying, the deadline is extended to at least 30 minutes.

Card field in the widget. If the tick box “Card field in the widget” is set in the payment settings (Invoicing → Overview), no new window is needed: the confirmation shows “Pay now right here”, and your customers pay by card or PayPal directly in the window above your page. Afterwards the widget returns to the confirmation and shows “paid” together with the invoice. Wallets such as Apple Pay and payment methods with a redirect such as Klarna still run via “More payment methods in a new window”. You do not need to change the embed code for this.

A single voucher. Pick “One specific voucher” at the top and the widget shows exactly one instead of the list (data-coupon="12") — as a card (data-variant="single"), as a plain button (data-variant="button") or as the full checkout page inside a frame (data-variant="page"). The configurator fills in the number for you.

The domain whitelist applies to the window and the embedded checkout as well: without your address on the list the frame stays empty or shows an error.

Existing embeds do not change: without the data-mode and data-coupon lines everything stays as before (new tab, all vouchers). To get the window onto your website, copy the code again and replace the old snippet.

Test that it works

  1. Open your website and make a test reservation.
  2. The booking appears immediately in the Day view and in the reservation list — which also completes the "test reservation" step of your Getting started list.
  3. Afterwards, cancel the test booking from the reservation list.

Group and company requests

Larger parties, company events and closed groups use a form of their own — with occasion, preferred date, number of participants, budget and extras. You can offer it right on your website instead of only linking to your page with us.

You find the embed code in the backoffice under Widget → Group requests. It loads group-v2.js and understands these settings:

  • data-variant="button" — a button on your page; the form opens on top of it. data-variant="inline" puts the form right into the page instead.
  • data-mode="modal" — your visitor stays on your page. data-mode="redirect" opens our request page in a new tab instead, in the language data-lang names. Applies to the button only.
  • data-label="Send a request" — your own button text. Without this line the widget default is used. With the embedded form it is the name of the frame a screen reader reads out.
  • data-color and data-lang as with the other widgets.

The same domain approval applies as for the other widgets: without an approved address the form shows an error instead of opening. And the same spam protection — there is nothing to set up.

Requests arrive in the backoffice under Requests, exactly like the ones from our own page. Your plan needs to include group requests.

Contact form

For everything that is not a reservation — a question about a voucher, an invoice, the next celebration — there is a contact form of its own: first name, last name, email, phone, topic and message. It is open to every business, whatever the plan.

You will find the embed code in the backoffice under Widget → Contact. It loads the same group-v2.js loader as the group request, with the line data-form="contact". All other settings (data-variant, data-mode, data-label, data-color, data-lang) work exactly as described above for group and company requests; without data-label the button reads “Contact us”. The same domain approval and the same spam protection apply.

Topics: You maintain the “Topic” choice on the same page. As long as none of your own topics is active, the form offers a default list (reservation, celebration or group, gift voucher, invoice, other). Use the default list creates these topics as rows of your own, which you can then rename, reorder, hide or delete. The chosen topic becomes the subject of the conversation.

For event providers: your default topics read “Appointment or course” and “Company event” instead of “Reservation” and “Celebration or group”, and the inbox buttons read Create as company request and Create as booking.

Your own page: Without embedding anything, the form also exists as a page of its own on our site — the link is in the “Your own page” box. Your business page shows a “Contact” button for it.

And then? Every request arrives as a conversation of its own in your inbox (filter “Contact request”), with the phone number ready to call. The guest receives a confirmation with a link to the conversation; your reply reaches them by email. In the header of the conversation you turn the request into a group request or into a reservation with one click: name, email, phone and the message are already filled in, and after saving, the conversation is attached to the new request or reservation — with an internal note the guest does not see.

For event providers

For you, the widget shows your bookable events instead of a table calendar. Embedding works identically: copy the code, approve your domain, test. The menu item Settings → Widget takes you straight to the events widget; the domain allow list is in the same row of tabs under Security, where you enter it yourself.

The events widget can additionally show a period filter above the grid — two date fields and a weekday selector. You switch it on in the widget configurator; the embed code then contains the line data-filters="1". Filtering happens directly in your visitors' browser, no further data is loaded. Existing embeds are unaffected: without that line everything stays as it is. For the change to reach your website, copy the code once more and replace it.