---
title: "What is CalDAV?"
url: https://meet.barq.dev/glossary/caldav
updated: 2026-11-17
author: "Hammad Ali"
---

# What is CalDAV?

> **Short answer:** CalDAV is a protocol used by calendar clients to access and update calendar data held on a server. It concerns the connection between applications, unlike a calendar file describing one appointment; for example, moving a 30-minute event from 09:00 to 10:00 requires the connected systems to exchange that change.


## What does CalDAV mean for a booking-app user?

CalDAV matters when your calendar account needs an explicitly supported connection to a scheduling application. A booking app must be able to check the calendar you use before you rely on that calendar's events to prevent conflicting appointments.


Check the connection first. CalDAV concerns the application's access to calendar data; a guest chooses an appointment through a public booking URL.


For a practical connection check, identify your calendar account, inspect the scheduler's supported connection methods, and confirm that the intended calendar appears in its conflict-checking selection. Don't infer support from a calendar-shaped icon or an invitation arriving successfully.


Check the product's connection documentation before choosing it. Provider support and account setup need explicit confirmation for the application you're choosing.


## Is CalDAV the same thing as iCalendar?

CalDAV concerns accessing calendar data, while iCalendar defines a calendar-data format. The checked [RFC 5545](https://www.rfc-editor.org/rfc/rfc5545) covers iCalendar, including `text/calendar` and the `ics` extension, as of 17 November 2026.


| Item | What it describes |
| --- | --- |
| CalDAV | Access between a calendar client and server |
| iCalendar | The calendar-data format named in RFC 5545 |
| ICS download | A file containing calendar information |
| Booking page | A guest's offered appointment choices |

Keep the layers apart. That RFC citation supports the format facts in this section; it isn't a claim that RFC 5545 defines the CalDAV connection protocol.


The [iCalendar explanation](https://meet.barq.dev/glossary/icalendar) covers the format. Our [two-way calendar sync definition](https://meet.barq.dev/glossary/two-way-calendar-sync) addresses the separate question of which changes travel between connected systems.


## Why does a moved appointment need more than a file?

A moved appointment changes the time that should count as occupied, so conflict checking needs current calendar information. A saved file for an earlier time can't tell a booking page that the host's commitment has since moved.


Use a simple example. A 30-minute call originally occupies 09:00 to 09:30, then moves to 10:00 to 10:30 on the same date without any change in its duration.


The interval that should block availability has shifted by sixty minutes. A scheduler still working from the original time could incorrectly offer 10:00, even though it correctly remembers that the appointment lasts half an hour.


This illustrates why connection behavior matters; it doesn't promise a particular polling interval, supported server or update speed for any CalDAV product.


## Does Barq Meet offer a CalDAV connection?

Barq Meet connects through the Google Calendar API instead of CalDAV. We offer Google account connections and calendar selection, so a host whose working calendar requires a CalDAV connection needs a scheduler that explicitly supports it.


Files don't add connections. We read selected Google calendars for conflicts and write the appointments booked through Barq Meet to the chosen Google calendar, a separate operation from attaching calendar information to a confirmation email.


We re-check Google calendar availability when a guest submits a booking. Importing an invitation into another calendar doesn't add that calendar to the host's connected conflict sources.


Browse [the wider scheduling glossary](https://meet.barq.dev/glossary/scheduling-glossary) for related connection terms. Check [the calendar coverage included](https://meet.barq.dev/pricing), or [connect a Google calendar for booking](https://meet.barq.dev/app/sign-in) if that's where you keep your working commitments.

## Frequently asked questions

### Does an ICS invitation mean CalDAV is connected?

No. Receiving a calendar-data file doesn't prove that a client has an ongoing calendar connection. Check the booking app's account connections before relying on it to detect changes in that calendar. Treat file-based invitations and live account connections as separate capabilities when deciding whether a product can check your existing diary.

### Should I paste calendar credentials into a booking description?

No. A booking description is information for guests, not a calendar connection setting. Keep account credentials out of public descriptions and connect calendars only through the application's intended account setup. Use the product's documented account connection process, keeping passwords and server credentials out of both guest-facing descriptions and appointment answers.

### What should I check before switching schedulers for CalDAV?

Check explicit support for your calendar account and the operations you need. Reading conflicts, writing booked appointments and handling changes are separate requirements; a general reference to calendar compatibility doesn't answer all of them. Verify the calendar server and authentication method your organization needs, then test a real busy interval through that exact connection.

## Related pages

- [What is iCalendar (RFC 5545)?](https://meet.barq.dev/glossary/icalendar)
- [What is two-way calendar sync?](https://meet.barq.dev/glossary/two-way-calendar-sync)
- [Scheduling glossary: booking and calendar terms explained](https://meet.barq.dev/glossary/scheduling-glossary)

[Create your free booking link](https://meet.barq.dev/app/sign-in)
