How can we help you?

Advanced documentation search

HEAD /instance/:instance/*?

Product: FeraCalendar Topic: API Versions: Applies to all documented versions Current
Written by user
Updated

Audience: Application developers
Editorial status: Published — Source Validated
Product: FeraCalendar
Classification: partner

HEAD /caldav/instance/{instance}/{path}

Overview

Authenticated 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.

Authentication and access

Security scheme: basicAuth

Control Contract
Authentication authenticated
Authorization HTTP Basic credentials are verified by FeraAuth and the resolved principal must have read capability for the selected calendar context.
Licensing The adapter has no separate local product-license middleware; it relies on FeraAuth credential verification and FeraCal calendar-access resolution for the effective instance.
Instance Context Principal and instance routes supply an instance UUID. Calendar routes first resolve the calendar UUID to its owner instance, then verify credentials in that effective context.
Ownership The verified FeraAuth user is resolved to a FeraCal person and calendar role; collection and event access is constrained to calendars for which that principal has the required capability.

Parameters

Name Location Type Required Description
instance path string (uuid) Yes FeraCal instance UUID used for CalDAV discovery and authorization.
path path string Yes Optional descendant resource path consumed by collection discovery or report routing.

Request body

No request body.

Example request

cURL

curl --request HEAD \ \
  --url 'https://caldav.feradel.com/caldav/instance/715c9ebb-0470-11f1-a928-0ed2cd1b87df/events' \
  --user '$FERA_CALDAV_USERNAME:$FERA_CALDAV_PASSWORD'

Responses

200 The authenticated principal has read access to the collection.

Header Description
DAV DAV compliance classes advertised by the adapter.
MS-Author-Via DAV authoring capability marker.
Allow Methods understood by the CalDAV adapter.

401 Basic credentials are missing or rejected.

Content type: application/json; schema: CalDavError

{
    "success": false,
    "error": {
        "message": "CalDAV credentials are required"
    }
}

403 The verified principal lacks calendar read access.

Content type: application/json; schema: CalDavError

{
    "success": false,
    "error": {
        "message": "Calendar read access denied"
    }
}

500 Credential or calendar dependency failed.

Content type: application/json; schema: CalDavError

{
    "success": false,
    "error": {
        "message": "Internal server error"
    }
}

Status and retry matrix

Status Condition Retryable Developer action
200 The authenticated principal has read access to the collection. No Continue with the DAV, XML, iCalendar, ETag, or empty-body result described for this status.
401 Basic credentials are missing or rejected. No Correct credentials, capability, resource name, XML/iCalendar content, UID, or ETag before retrying.
403 The verified principal lacks calendar read access. No Correct credentials, capability, resource name, XML/iCalendar content, UID, or ETag before retrying.
500 Credential or calendar dependency failed. Yes Correct credentials, capability, resource name, XML/iCalendar content, UID, or ETag before retrying.

Related operations and events

  • Operation caldav_options_2
  • Operation caldav_head_3
  • Operation caldav_head_4
  • Operation caldav_options_7

Source trace

Repository: feradelinc/feradel.calendar.caldav
Route: src/caldav/router.js
Handler: controller.headCollection
Line: 26
Contract: OpenAPI 3.1, source-traced and publication-validated.