How do availability requests work?

When a host doesn’t have availability on a specific date you can send him/her a request for availability. In order to request availability you:

  1. Go to the experience page of the host
  2. You hit the yellow ‘Request Availability’ button
  3. You select the date on which you want to book the experience
  4. You fill in your full name and email address
  5. And you leave a message in which you inform the host about the details of your request such as the preferred time on which the experience should take place and the amount of people that will participate in the experience
  6. You then click on ‘Send Request’

We'll send your request along to the host. The host will then have an opportunity to respond and/or add your requested date to his calendar so that you can book the experience. You will be notified via ‘Notifications’ and email as soon as a host replied to your request.

As a host you will be notified via ‘Notifications’, email and you can view all your availability requests in the following way:

  1. Login to your account
  2. Click on your avatar and then on ‘My Experiences’
  3. Click on the blue square (just below ‘Edit’) for which you received a request
  4. Click on ‘Availability’ and then scroll all the way down to ‘Availability Requests’
  5. The requests that still need to be answered are marked as ‘Response Required’. You can simply reply to each request by clicking on the arrow (below ‘Action’)
  6. You then have 2 options: a) I have availability for the requested date or b) I don’t have availability for the requested date. You can leave a personal message as well. If you have availability we advise you to first add the requested date to your calendar before replying to a request

If you have availability, you’ve added the requested date to your calendar and you’ve replied to the request, a traveler will be able to book your experience.

Please wait...
Thank you!

Your submission has been received, we will review it shortly.


It looks like your submission was not sent. Please try again.