Skip to content
nofeb

What is CalDAV?

Also called Calendaring Extensions to WebDAV

CalDAV is the standard protocol calendar apps use to read and write calendars kept on a server. Defined in RFC 4791 as an extension of WebDAV, it stores each event as an iCalendar object at its own URL and lets clients such as Apple Calendar, Thunderbird and DAVx⁵ query by time range and sync only what changed.

Checked against the engine on .

Shipped nofeb's support for CalDAV

How does CalDAV work?

A CalDAV server exposes a principal for each user, a calendar home under it, and one collection per calendar. Clients find them through /.well-known/caldav (RFC 6764), list them with PROPFIND, and read events with REPORT queries: calendar-query for a time range, calendar-multiget for named events, and sync-collection (RFC 6578) for everything changed since a sync token.

Writes are HTTP PUTs of iCalendar text guarded by ETags: If-Match stops a client overwriting a change it has not seen, and If-None-Match: * creates an event only if none exists at that URL. Inviting people is a separate layer: either the server sends the invitations for the client, or the client emails them itself as iMIP messages.

For software, the value of CalDAV is reach. Anything that syncs with a CalDAV server, which covers most calendar apps outside the big providers' own, can show and edit the same events an agent manages, without an integration for each app.

Events in one week
REPORT /dav/calendars/inb_…/cal_…/ HTTP/1.1
Depth: 1
Content-Type: application/xml

<C:calendar-query xmlns:D="DAV:" xmlns:C="urn:ietf:params:xml:ns:caldav">
  <D:prop><D:getetag/><C:calendar-data/></D:prop>
  <C:filter><C:comp-filter name="VCALENDAR"><C:comp-filter name="VEVENT">
    <C:time-range start="20261005T000000Z" end="20261012T000000Z"/>
  </C:comp-filter></C:comp-filter></C:filter>
</C:calendar-query>

How does nofeb use CalDAV?

  • Every nofeb inbox has calendars, served over CalDAV under /dav/ with discovery at /.well-known/caldav: principals, calendar homes, PROPFIND, PROPPATCH, calendar-query, calendar-multiget, sync-collection and free-busy-query, and GET, PUT and DELETE with ETags.
  • Clients sign in with HTTP Basic: the inbox address as the username and an app password or API key as the password, the same credential a phone uses for IMAP. A bearer token works too.
  • Changes made over CalDAV never email anyone; the client sends its own invitations. Events and bookings made over the API or MCP send theirs through the inbox's sending policy. New calendars are created over the API, not with MKCALENDAR.
  • Each event is kept as its full iCalendar object, so alarms, X- properties and attendee parameters written by a client survive edits made over the API, JMAP or the webmail, and the API, JMAP and CalDAV all read the same change history.

Frequently asked questions

Should an AI agent use CalDAV directly?

Usually not. The API's availability, free/busy and booking calls, and the matching MCP tools, do in one call what CalDAV needs several requests for. CalDAV is how people's own calendar apps see the same calendar as the agent.

Why does my CalDAV client not send invitations through nofeb?

nofeb's CalDAV server does not offer to schedule on the client's behalf, so the client emails invitations itself. Use the API or MCP when you want nofeb to send them under the inbox's autonomy tier.

Status of everything on this page

Every capability named above, with its status as reconciled against the engine.

CapabilityWhat it doesStatus
Calendar per inbox A calendar on every inbox: events with recurrence and time zones, invitations, updates, cancellations and replies by email, auto-accept rules, free/busy, availability and booking that sends the invitations, MCP tools for scheduling, and CalDAV and JMAP Calendars for standard clients. Invitations an agent sends follow its inbox's autonomy tier. Shipped
IMAP and POP3 IMAP4rev2 (with IMAP4rev1 compatibility, IDLE, CONDSTORE and QRESYNC) and POP3 on every inbox, over TLS only, signed in with the inbox address and an API key or a revocable per-inbox app password. Shipped
JMAP JMAP Mail, submission, vacation responses and push, one account per inbox a key can see, sharing one change history with the API and IMAP, with extensions for typed metadata and approvals. A send over JMAP meets the same autonomy tiers as any other. Shipped