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.

Calendar API

Owning App
Calendar
Contract version
1.20.0
Audience
vision-calendar
Workspace binding
Calendar workspace reference required

Download the authoritative OpenAPI 3.1 definition

46 operations

Generated from Vision Calendar API 1.20.0

Vision Calendar MCP

MCPpreview

This is an authoritative capability inventory derived from Calendar's HTTP authority, not a reachable MCP transport. Any future MCP adapter must call the Calendar API without weakening actor binding, app entitlement, workspace isolation, operation scopes, record-version concurrency, or idempotency. Provider connection and external notification delivery remain unavailable.

Version
1.0.1
Authority
calendar_http_contract_only
Transport
capability-inventory-only
Required scope
Operation-specific Calendar scope from the authoritative OpenAPI x-required-scope; write operations also require an Idempotency-Key

Approved capabilities

  • list_calendars
  • create_calendar
  • list_events
  • get_event
  • create_event
  • update_event
  • cancel_event
  • respond_to_invitation
  • find_available_slots
  • create_request_call_hold
  • confirm_request_call
  • release_request_call_hold
  • cancel_request_call_event
  • list_provider_connections

Explicitly prohibited

  • bypass_actor_binding
  • bypass_workspace_scope
  • bypass_operation_scope
  • replay_idempotency_key_with_different_body
  • claim_external_notification_delivery
  • connect_google_account
  • connect_microsoft_account
  • reveal_provider_tokens
  • issue_public_rsvp_link
  • run_sql

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.