Skip to main content

Booking Parameters

Our static booking engine has a lot of GET parameters which shows you the right date, number of persons or an accommodation type, forced price etc In this chapter we will inform you about the possibilities of the static booking engine

A demo can be found here:

GET Parameters

Get parameters are send to the booking engine in the following format:

Replace demo in the url with your own camping slug.

In the url there are a specific amount of parameters are defined.

  • arrival
  • departure
  • accommodation
  • guests
  • birthdates
  • category
  • admin_id (for ota's only)
  • channel_id (for ota's only)
  • hide_filter
  • modes
  • view
  • show_camping_name
  • discountcard
  • show_discount_card
  • persons
  • website_url
  • back_url
  • object_id
  • lang
  • default_days
  • _gl


The arrival is used to set a specific arrival date in the booking engine The arrival is in format 'YYYY-MM-DD'


The departure is used to set a specific departure date in the booking engine The departure is in format 'YYYY-MM-DD'


The age table input is a json/ url encoded string. You can set the guests for the booking engine by using the age table ids from the system. The age_table_input looks like this : '[{"id": 12345, "count": 2}, {"id": 12346, "count": 1}]'


If you don't have information about the guest as above. You are also able to send over the birthdays of the guest. We will convert them to the right age tables. The guest_birthdays parameter shout be like this: [{"birthdate":"2015-01-01","amount":1}, {"birthdate":"2004-02-01","amount":2}] (The json object should be url encoded)

In this case there is one child born at 2020-01-01 and one adult born in 2004-02-01.


The accommodation id to be selected by default. Required if you load the accommodation or cart view


The category of the accommodations, this can be rent or camp.


If you are an OTA, you are able to send the admin_id along with the request. This indicates what campsite you want to book.


Hide the category filter of rent / camp if you don't need this.


This can be production (default) or test.


This can be filter (default), accommodation, cart, map. Important: The accommodation parameter is also required to move to this view


Should we show the campsite name (default we don't show this)


The discount card ID we should preselect


Show the possibility to select a discount card on the filter page.


The default amount of persons selected


To what url should we redirect the user if he / she clicks on the back button on the home / filter page.


We will force the user back to this url, whenever he hits the back button.


Should we pre select a object ID (Place or Room ID)? This is only possible if the object is part of the selected accommodation


Force a specific language (ISO 639-1 codes) to be used. By default we use the users Browser language. If this does not exists we fall back on en.


By default the amount of days selected is 7. You can change this by sending a default number of days. Will be overwritten if you use the arrival or departure parameter.


The code for Google Analytics multi domain tracking.

Example form

<form action="" method="get">

<label for="category">Rent or Camp?</label>
<select id="category" name="category">
<option value="" selected>Select your category</option>
<option value="rent">Rental Accommodations</option>
<option value="camp">Camping</option>
<label for="arrival">Arrival:</label>
<input type="date" id="arrival" name="arrival"><br><br>
<label for="departure">Departure:</label>
<input type="date" id="departure" name="departure"><br><br>
<input type="submit" value="Search and Book">


The form action can be changed to your bookings url which can be found in the website integration page:

Choose the option hosted bookings site.