Implements controller.get in routes/api/v1/person/routes.js:10. The authenticated boundary enforces managed-product and owner/member role rules, uses owner-scoped keys/UUIDs, applies visibility masks only after access resolution, and records mutations.
Applies to all documented versionsImplements controller.get in routes/api/v1/resource/routes.js:11. The authenticated boundary enforces managed-product and owner/member role rules, uses owner-scoped keys/UUIDs, applies visibility masks only after access resolution, and records mutations.
Applies to all documented versionsImplements controller.createOrUpdate in routes/api/v1/calendar/routes.js:8. The authenticated boundary enforces managed-product and owner/member role rules, uses owner-scoped keys/UUIDs, applies visibility masks only after access resolution, and records mutations.
Applies to all documented versionsImplements controller.createOrUpdate in routes/api/v1/person/routes.js:8. The authenticated boundary enforces managed-product and owner/member role rules, uses owner-scoped keys/UUIDs, applies visibility masks only after access resolution, and records mutations.
Applies to all documented versionsImplements controller.createOrUpdate in routes/api/v1/resource/routes.js:8. The authenticated boundary enforces managed-product and owner/member role rules, uses owner-scoped keys/UUIDs, applies visibility masks only after access resolution, and records mutations.
Applies to all documented versionsImplements controller.createOrUpdate in routes/api/v1/event/routes.js:8. The authenticated event boundary resolves the requested calendar and actor, enforces owner/editor/inviter rules, preserves recurrence, and joins attendee/resource invitation state without treating visibility as authorization by itself.
Applies to all documented versionsAuthenticated conditional event deletion implemented at src/caldav/router.js:43 (controller.deleteEvent). The adapter validates the UUID .ics resource, checks write capability and If-Match against the current ETag, and removes the corresponding FeraCal event.
Applies to all documented versionsImplements controller.delete in routes/api/v1/calendar/routes.js:17. The authenticated boundary enforces managed-product and owner/member role rules, uses owner-scoped keys/UUIDs, applies visibility masks only after access resolution, and records mutations.
Applies to all documented versionsImplements controller.delete in routes/api/v1/person/routes.js:12. The authenticated boundary enforces managed-product and owner/member role rules, uses owner-scoped keys/UUIDs, applies visibility masks only after access resolution, and records mutations.
Applies to all documented versionsImplements controller.delete in routes/api/v1/person/routes.js:11. The authenticated boundary enforces managed-product and owner/member role rules, uses owner-scoped keys/UUIDs, applies visibility masks only after access resolution, and records mutations.
Applies to all documented versionsImplements controller.delete in routes/api/v1/resource/routes.js:13. The authenticated boundary enforces managed-product and owner/member role rules, uses owner-scoped keys/UUIDs, applies visibility masks only after access resolution, and records mutations.
Applies to all documented versionsImplements controller.delete in routes/api/v1/resource/routes.js:12. The authenticated boundary enforces managed-product and owner/member role rules, uses owner-scoped keys/UUIDs, applies visibility masks only after access resolution, and records mutations.
Applies to all documented versionsImplements controller.delete in routes/api/v1/event/routes.js:16. The authenticated event boundary resolves the requested calendar and actor, enforces owner/editor/inviter rules, preserves recurrence, and joins attendee/resource invitation state without treating visibility as authorization by itself.
Applies to all documented versionsImplements controller.delete in routes/api/v1/event/routes.js:15. The authenticated event boundary resolves the requested calendar and actor, enforces owner/editor/inviter rules, preserves recurrence, and joins attendee/resource invitation state without treating visibility as authorization by itself.
Applies to all documented versionsDAV capability responder implemented at src/caldav/router.js:12 (controller.options). It advertises compliance classes and supported methods without requiring Basic credentials or exposing tenant calendar data.
Applies to all documented versionsPublic liveness probe implemented at src/app.js:29 (inline health). It reports only process availability and does not verify FeraAuth, FeraCal, storage, or downstream readiness.
Applies to all documented versionsAuthenticate REST and CalDAV requests
Applies to all documented versionsDiscover, synchronize, retrieve, and mutate calendars over CalDAV
Applies to all documented versionsAuthenticated event retrieval implemented at src/caldav/router.js:41 (controller.getEvent). A UUID .ics resource is resolved through the authorized calendar and returned as text/calendar with its deterministic ETag.
Applies to all documented versionsAuthenticated collection probe implemented at src/caldav/router.js:31 (controller.headCollection). Basic credentials are verified through FeraAuth with instance/calendar context before FeraCal read capability is confirmed.
Applies to all documented versionsAuthenticated collection probe implemented at src/caldav/router.js:32 (controller.headCollection). Basic credentials are verified through FeraAuth with instance/calendar context before FeraCal read capability is confirmed.
Applies to all documented versionsAuthenticated collection probe implemented at src/caldav/router.js:38 (controller.headCollection). Basic credentials are verified through FeraAuth with instance/calendar context before FeraCal read capability is confirmed.
Applies to all documented versionsAuthenticated collection probe implemented at src/caldav/router.js:21 (controller.headCollection). Basic credentials are verified through FeraAuth with instance/calendar context before FeraCal read capability is confirmed.
Applies to all documented versionsAuthenticated collection probe implemented at src/caldav/router.js:22 (controller.headCollection). Basic credentials are verified through FeraAuth with instance/calendar context before FeraCal read capability is confirmed.
Applies to all documented versionsAuthenticated collection probe implemented at src/caldav/router.js:26 (controller.headCollection). Basic credentials are verified through FeraAuth with instance/calendar context before FeraCal read capability is confirmed.
Applies to all documented versionsAuthenticated collection probe implemented at src/caldav/router.js:14 (controller.headCollection). Basic credentials are verified through FeraAuth with instance/calendar context before FeraCal read capability is confirmed.
Applies to all documented versionsAuthenticated collection probe implemented at src/caldav/router.js:15 (controller.headCollection). Basic credentials are verified through FeraAuth with instance/calendar context before FeraCal read capability is confirmed.
Applies to all documented versionsImplements controller.invite in routes/api/v1/event/routes.js:9. The authenticated event boundary resolves the requested calendar and actor, enforces owner/editor/inviter rules, preserves recurrence, and joins attendee/resource invitation state without treating visibility as authorization by itself.
Applies to all documented versionsImplements controller.access in routes/api/v1/calendar/routes.js:11. The authenticated boundary enforces managed-product and owner/member role rules, uses owner-scoped keys/UUIDs, applies visibility masks only after access resolution, and records mutations.
Applies to all documented versionsImplements controller.get in routes/api/v1/calendar/routes.js:14. The authenticated boundary enforces managed-product and owner/member role rules, uses owner-scoped keys/UUIDs, applies visibility masks only after access resolution, and records mutations.
Applies to all documented versionsImplements controller.get in routes/api/v1/calendar/routes.js:15. The authenticated boundary enforces managed-product and owner/member role rules, uses owner-scoped keys/UUIDs, applies visibility masks only after access resolution, and records mutations.
Applies to all documented versionsImplements controller.get in routes/api/v1/event/routes.js:10. The authenticated event boundary resolves the requested calendar and actor, enforces owner/editor/inviter rules, preserves recurrence, and joins attendee/resource invitation state without treating visibility as authorization by itself.
Applies to all documented versionsImplements controller.get in routes/api/v1/event/routes.js:14. The authenticated event boundary resolves the requested calendar and actor, enforces owner/editor/inviter rules, preserves recurrence, and joins attendee/resource invitation state without treating visibility as authorization by itself.
Applies to all documented versionsImplements controller.get in routes/api/v1/event/routes.js:13. The authenticated event boundary resolves the requested calendar and actor, enforces owner/editor/inviter rules, preserves recurrence, and joins attendee/resource invitation state without treating visibility as authorization by itself.
Applies to all documented versionsImplements controller.get in routes/api/v1/resource/routes.js:9. The authenticated boundary enforces managed-product and owner/member role rules, uses owner-scoped keys/UUIDs, applies visibility masks only after access resolution, and records mutations.
Applies to all documented versionsDAV capability responder implemented at src/caldav/router.js:29 (controller.options). It advertises compliance classes and supported methods without requiring Basic credentials or exposing tenant calendar data.
Applies to all documented versionsDAV capability responder implemented at src/caldav/router.js:30 (controller.options). It advertises compliance classes and supported methods without requiring Basic credentials or exposing tenant calendar data.
Applies to all documented versionsDAV capability responder implemented at src/caldav/router.js:37 (controller.options). It advertises compliance classes and supported methods without requiring Basic credentials or exposing tenant calendar data.
Applies to all documented versionsDAV capability responder implemented at src/caldav/router.js:19 (controller.options). It advertises compliance classes and supported methods without requiring Basic credentials or exposing tenant calendar data.
Applies to all documented versionsDAV capability responder implemented at src/caldav/router.js:20 (controller.options). It advertises compliance classes and supported methods without requiring Basic credentials or exposing tenant calendar data.
Applies to all documented versionsDAV capability responder implemented at src/caldav/router.js:25 (controller.options). It advertises compliance classes and supported methods without requiring Basic credentials or exposing tenant calendar data.
Applies to all documented versionsAuthenticated DAV discovery implemented at src/caldav/router.js:33 (controller.propfind). Depth controls whether child collections are included; returned XML covers principal/home/calendar properties, supported reports, sync/ETag metadata, and effective privileges.
Applies to all documented versionsAuthenticated DAV discovery implemented at src/caldav/router.js:34 (controller.propfind). Depth controls whether child collections are included; returned XML covers principal/home/calendar properties, supported reports, sync/ETag metadata, and effective privileges.
Applies to all documented versionsAuthenticated DAV discovery implemented at src/caldav/router.js:39 (controller.propfind). Depth controls whether child collections are included; returned XML covers principal/home/calendar properties, supported reports, sync/ETag metadata, and effective privileges.
Applies to all documented versionsAuthenticated DAV discovery implemented at src/caldav/router.js:23 (controller.propfind). Depth controls whether child collections are included; returned XML covers principal/home/calendar properties, supported reports, sync/ETag metadata, and effective privileges.
Applies to all documented versionsAuthenticated DAV discovery implemented at src/caldav/router.js:24 (controller.propfind). Depth controls whether child collections are included; returned XML covers principal/home/calendar properties, supported reports, sync/ETag metadata, and effective privileges.
Applies to all documented versionsAuthenticated DAV discovery implemented at src/caldav/router.js:27 (controller.propfind). Depth controls whether child collections are included; returned XML covers principal/home/calendar properties, supported reports, sync/ETag metadata, and effective privileges.
Applies to all documented versionsAuthenticated DAV discovery implemented at src/caldav/router.js:16 (controller.propfind). Depth controls whether child collections are included; returned XML covers principal/home/calendar properties, supported reports, sync/ETag metadata, and effective privileges.
Applies to all documented versionsAuthenticated DAV discovery implemented at src/caldav/router.js:17 (controller.propfind). Depth controls whether child collections are included; returned XML covers principal/home/calendar properties, supported reports, sync/ETag metadata, and effective privileges.
Applies to all documented versionsAuthenticated conditional event write implemented at src/caldav/router.js:42 (controller.putEvent). The adapter validates one VEVENT, requires its UID to match the UUID .ics filename, checks write capability and If-Match, then creates or updates the…
Applies to all documented versionsFeraCal directly posts one exact-body HMAC callback after lifecycle success or failure. There is no internal retry loop; a failed success callback fails the source request so FeraHooks can redeliver the idempotent…
Applies to all documented versionsAuthenticated CalDAV report implemented at src/caldav/router.js:35 (controller.report). The adapter parses calendar-query time ranges, multiget href UUIDs, or sync-collection intent and returns authorized events, ETags, and iCalendar in DAV multistatus XML.
Applies to all documented versionsAuthenticated CalDAV report implemented at src/caldav/router.js:36 (controller.report). The adapter parses calendar-query time ranges, multiget href UUIDs, or sync-collection intent and returns authorized events, ETags, and iCalendar in DAV multistatus XML.
Applies to all documented versionsAuthenticated CalDAV report implemented at src/caldav/router.js:40 (controller.report). The adapter parses calendar-query time ranges, multiget href UUIDs, or sync-collection intent and returns authorized events, ETags, and iCalendar in DAV multistatus XML.
Applies to all documented versionsImplements controller.resolve in routes/api/v1/calendar/routes.js:13. The authenticated boundary enforces managed-product and owner/member role rules, uses owner-scoped keys/UUIDs, applies visibility masks only after access resolution, and records mutations.
Applies to all documented versionsImplements controller.resolveAccess in routes/api/v1/calendar/routes.js:12. The authenticated boundary enforces managed-product and owner/member role rules, uses owner-scoped keys/UUIDs, applies visibility masks only after access resolution, and records mutations.
Applies to all documented versionsHandle JSON, DAV XML, iCalendar, and empty-body responses
Applies to all documented versionsImplements controller.one in routes/api/v1/calendar/routes.js:16. The authenticated boundary enforces managed-product and owner/member role rules, uses owner-scoped keys/UUIDs, applies visibility masks only after access resolution, and records mutations.
Applies to all documented versionsImplements controller.get in routes/api/v1/event/routes.js:11. The authenticated event boundary resolves the requested calendar and actor, enforces owner/editor/inviter rules, preserves recurrence, and joins attendee/resource invitation state without treating visibility as authorization by itself.
Applies to all documented versionsImplements controller.get in routes/api/v1/event/routes.js:12. The authenticated event boundary resolves the requested calendar and actor, enforces owner/editor/inviter rules, preserves recurrence, and joins attendee/resource invitation state without treating visibility as authorization by itself.
Applies to all documented versionsImplements controller.get in routes/api/v1/person/routes.js:9. The authenticated boundary enforces managed-product and owner/member role rules, uses owner-scoped keys/UUIDs, applies visibility masks only after access resolution, and records mutations.
Applies to all documented versionsImplements controller.get in routes/api/v1/resource/routes.js:10. The authenticated boundary enforces managed-product and owner/member role rules, uses owner-scoped keys/UUIDs, applies visibility masks only after access resolution, and records mutations.
Applies to all documented versionsImplements controller.share in routes/api/v1/calendar/routes.js:9. The authenticated boundary enforces managed-product and owner/member role rules, uses owner-scoped keys/UUIDs, applies visibility masks only after access resolution, and records mutations.
Applies to all documented versionsSource-supported CalActor schema for FeraCalendar integrations.
Applies to all documented versionsSource-supported CalDavError schema for FeraCalendar integrations.
Applies to all documented versionsSource-supported Calendar schema for FeraCalendar integrations.
Applies to all documented versionsSource-supported CalendarEvent schema for FeraCalendar integrations.
Applies to all documented versionsSource-supported CalError schema for FeraCalendar integrations.
Applies to all documented versionsSource-supported CalMutation schema for FeraCalendar integrations.
Applies to all documented versionsSource-supported CalResult schema for FeraCalendar integrations.
Applies to all documented versionsSource-supported HealthResponse schema for FeraCalendar integrations.
Applies to all documented versionsSource-supported LifecycleAcknowledgment schema for FeraCalendar integrations.
Applies to all documented versionsSource-supported LifecycleEvent schema for FeraCalendar integrations.
Applies to all documented versionsImplements controller.unshare in routes/api/v1/calendar/routes.js:10. The authenticated boundary enforces managed-product and owner/member role rules, uses owner-scoped keys/UUIDs, applies visibility masks only after access resolution, and records mutations.
Applies to all documented versions