Wroot Calendar API (v1)
Read endpoints are public and unauthenticated. Write endpoints need a per-calendar API key, created from a calendar's API keys admin page. The path is versioned and additive-only: existing fields keep their meaning, and new optional ones may appear without notice.
Reading events
No auth required. CORS is open ("*"), so these can be called from the browser.
curl "https://calendar.wrootlabs.com/api/v1/calendars/riotexas/events?from=2026-10-01&to=2026-11-01"from/to are local dates in the calendar's own time zone, the window is half-open (to exclusive), and the span can't exceed 366 days. Add &category=worship to filter by category slug.
Creating an event
curl -X POST "https://calendar.wrootlabs.com/api/v1/calendars/riotexas/events" \
-H "Authorization: Bearer wc_live_..." \
-H "Content-Type: application/json" \
-d '{
"title": "Sunday Service",
"timezone": "America/Chicago",
"allDay": false,
"start": "2026-10-04T10:00:00",
"end": "2026-10-04T11:00:00",
"rrule": "FREQ=WEEKLY;BYDAY=SU",
"categories": ["worship"],
"status": "published"
}'start/end are wall-clock local times in timezone -- never an offset or Z. All-day events send YYYY-MM-DD dates instead. rrule is RFC 5545 without DTSTART, or omit it for a single occurrence. status defaults to "published"; set it to "draft" or "pending" to hold the event for review in the admin UI instead. Responds 201 with { "id": "...", "slug": "..." }.
Editing an event
Without scope, a PATCH replaces the event's own content and timing:
curl -X PATCH "https://calendar.wrootlabs.com/api/v1/calendars/riotexas/events/{eventId}" \
-H "Authorization: Bearer wc_live_..." \
-H "Content-Type: application/json" \
-d '{
"title": "Sunday Service (moved)",
"timezone": "America/Chicago",
"allDay": false,
"start": "2026-10-04T10:30:00",
"end": "2026-10-04T11:30:00"
}'For a recurring series, add ?scope=this|following|all&occurrence={id} to change one occurrence's time instead of the series' own definition -- occurrence is the YYYYMMDDTHHmm id embedded in every occurrence the events endpoint returns. Only start/end apply in this mode; content changes go through the scope-less form above.
curl -X PATCH ".../events/{eventId}?scope=this&occurrence=20261011T1000" \
-H "Authorization: Bearer wc_live_..." \
-H "Content-Type: application/json" \
-d '{ "start": "2026-10-11T11:00:00", "end": "2026-10-11T12:00:00" }'Deleting an event
curl -X DELETE "https://calendar.wrootlabs.com/api/v1/calendars/riotexas/events/{eventId}" \
-H "Authorization: Bearer wc_live_..."Deletes the whole event (and every occurrence of a series). Add ?scope=this|following&occurrence={id} to remove just one occurrence or truncate the series from one forward; scope=all deletes the whole event, same as no scope at all.
Errors and limits
401-- missing, unknown, or revoked key, or a key that's valid for a different calendar.429-- more than 60 write requests in a rolling minute for that key.400-- a validation error; the body'serrorfield says which.