Calendar developer access
Agendas, events, availability, conflicts, recurrence, attendance responses, and expiring scheduling holds.
- Owner
- Vision Calendar
- Lifecycle
- preview
- Runtime
- restricted
- App entitlement
- calendar
- Audience
- vision-calendar
- Workspace
- Calendar workspace reference required
Authority boundary
Calendar owns scheduling resources, workspace and actor bindings, visibility, recurrence, conflict, and concurrency rules.
Complete preview contract: Every operation and MCP capability in the approved definitions below is documented. The lifecycle and runtime labels describe stability and availability, not partial catalog coverage.
Calendar API
- Owning App
- Calendar
- Contract version
- 1.6.0
- Audience
- vision-calendar
- Workspace binding
- Calendar workspace reference required
Download the authoritative OpenAPI 3.1 definition
16 operations
Generated from Vision Calendar API 1.6.0
- GET/health/live
Process liveness
No bearer scope declaredFull operation reference → Version and contract metadata
No bearer scope declaredFull operation reference →OpenAPI contract
No bearer scope declaredFull operation reference →Authenticated schema readiness
Full operation reference →calendar:health:readProvision or reactivate a Vision human actor binding
Full operation reference →calendar:actor:provisionAuthorized, visibility-filtered agenda
Full operation reference →calendar:agenda:readAuthorized event details
Full operation reference →calendar:event:readWorking hours, exceptions, and free/busy without event details
Full operation reference →calendar:availability:readFind event and active-hold conflicts without record details
Full operation reference →calendar:conflict:readCreate, update, or cancel a locally authoritative event
Full operation reference →calendar:event:writeRecord the authorized actor's response to an internal invitation
Full operation reference →calendar:attendance:writeModify or cancel one materialized occurrence in a local series
Full operation reference →calendar:recurrence:writeCreate or release an expiring scheduling hold
Full operation reference →calendar:hold:writeOpen bookable slots across one or more actors
Full operation reference →calendar:availability:readSet working hours, or create and delete availability exceptions
Full operation reference →calendar:availability:writeCalendar's interface, described for this caller
Full operation reference →calendar:agenda:read
Publication evidence
This page is generated from the approval registry. Contract checksums, source drift, security declarations, scopes, references, and operation identifiers are verified before publication. A production documentation deployment remains a separate approval and rollback gate.