1. Knowledge Base
  2. Connections
  3. Connecting with OTAs using iCals

Amending iCal feeds with filters and MIME type support

Choose what booking data you share with external calendars or OTAs - and keep full control

Filtering iCal feeds

You can now control which types of bookings are exported via your iCal feeds by adding filters to the iCal URL.

There are three available filters:

1. Direct bookings and blocked dates only. (add 0/direct/):

https://anytimeholidays.anytimebooking.eu/google/ical/[UNIT_ID]/0/direct/feed.ics

2. Third-party (OTA) bookings only (add 0/ota/):

https://anytimeholidays.anytimebooking.eu/google/ical/[UNIT_ID]/0/ota/feed.ics

3. All events (direct, OTA, and blocked dates). (add 0/all/):

https://anytimeholidays.anytimebooking.eu/google/ical/[UNIT_ID]/0/all/feed.ics

 

where [UNIT_ID] is the unit reference from your account.


Sub-Units

If the unit is a sub-unit, you’ll need to ensure there is a SUB-UNIT_ID after the UNIT_ID in the URL.

For example, a direct bookings only feed for sub-unit 32407 would be:
https://anytimeholidays.anytimebooking.eu/google/ical/[UNIT_ID]/[sub-unit]/direct/feed.ics


MIME type compatibility

Some OTAs may experience issues importing iCal feeds due to the MIME type used. To resolve this, you can append the parameter ?mime=calendar to the end of the feed URL.

For example:

https://anytimeholidays.anytimebooking.eu/google/ical/[UNIT_ID]/[sub-unit]/feed.ics?mime=calendar

You can combine this with filters as well. For instance, a direct bookings feed with MIME type specified would be:

 https://anytimeholidays.anytimebooking.eu/google/ical/[UNIT_ID]/[sub-unit]/direct/feed.ics?mime=calendar
 
Summary
  • Add /direct/, /ota/, or /all/ to filter the type of bookings exported.

  • Include /0/ in the path if the feed is for a parent unit.

  • Use ?mime=calendar to improve compatibility with OTAs that require a specific MIME type.