recurrence to create a repeating series in the same call.
Parameters
Event title. 1–200 characters.
Start datetime, ISO 8601 with offset, e.g.
2026-07-14T10:00:00+02:00. For a series, the first occurrence.End datetime, ISO 8601 with offset. Must be after
start.1–50 attendee email addresses. Each receives an invitation.
A CalDAV URL from
list_calendars. Defaults to the user’s default calendar.Event description, up to 5,000 characters.
Event location, up to 500 characters.
Turns the event into a repeating series; omit for a one-off event. Two forms:Structured object:
Raw RRULE string: a single-line iCalendar RRULE starting with
| Field | Type | Notes |
|---|---|---|
frequency | "daily" | "weekly" | "monthly" | "yearly" | Required |
interval | integer 1–1000 | Repeat every N periods; defaults to 1 (2 with weekly = fortnightly) |
byDay | array of MO TU WE TH FR SA SU | 1–7 weekday codes (RFC 5545) |
until | ISO 8601 with offset | Series stops after this instant. Mutually exclusive with count |
count | integer 1–1000 | Total occurrences. Mutually exclusive with until |
FREQ=, up to 1,000 characters, e.g. FREQ=WEEKLY;BYDAY=TH or FREQ=DAILY;COUNT=10. Express UNTIL as a UTC date-time (UNTIL=20261231T000000Z). Raw rules are only lightly validated — malformed rules surface as server errors.Example
Call
Result
uid — it identifies the event for updates, deletion, and RSVPs.
Errors
Event end must be after its start.No calendar available to create the event in.— the user has no calendar and none was specified.Calendar not found: <url>— thecalendarUrldidn’t resolve.Provide at most one of `until` or `count`, not both.— conflicting series bounds.