/calendar/v1/recurrence-commandsModify or cancel one materialized occurrence in a local series
The approved contract does not provide a longer purpose statement for this operation.
- App
- Calendar
- Contract
- Calendar API 1.6.0
- Lifecycle
- preview
- Runtime
- restricted
- Operation ID
- Not declared (legacy exception)
- Canonical origin
- Not declared; gateway routing required
Availability: This is a preview contract with runtime status restricted. Publication documents an approved interface; it does not imply public production access.
Purpose and use cases
Modify or cancel one materialized occurrence in a local series
The owning App is Vision Calendar. Calendar owns scheduling resources, workspace and actor bindings, visibility, recurrence, conflict, and concurrency rules.
Business use cases and out-of-scope behavior are not yet declared in the approved OpenAPI description.
Request
POST /calendar/v1/recurrence-commands
This contract intentionally declares no direct server URL. Obtain the routed App origin before attempting the request.
Authentication and authorization
Send a Vision-issued bearer token for the exact App audience. The token must include the calendar entitlement and satisfy the calendar workspace reference required binding.
- Required scope:
calendar:recurrence:write
Human roles are not declared in OpenAPI. Record-level and business permission checks remain the owning App's authority.
Headers
Authorization: Bearer <access-token>— required.Accept: application/json— recommended where a JSON response is declared.Content-Type: application/json— required for the documented request representation.
Undeclared tracing, idempotency, conditional-request, and version headers are not assumed on this page.
Path and query parameters
| Name | Location | Type | Rules | Description |
|---|---|---|---|---|
| Idempotency-Key | header | string | required; minimum length 16; maximum length 160; pattern ^[A-Za-z0-9._:-]+$ | Actor-scoped key. Reusing it with an identical parsed command replays the durable result; reusing it for a different command returns IDEMPOTENCY_CONFLICT. |
Request body
Media type: application/json. The body is required.
object | objectRunnable examples
Placeholder values are generated from the approved schema and are not live credentials or customer data. Replace every angle-bracket or shell variable value. Examples cannot be run until the App has a routed base URL and your client has the required grant.
curl '${APP_BASE_URL}/calendar/v1/recurrence-commands' \
--request POST \
--header 'authorization: Bearer ${ACCESS_TOKEN}' \
--header 'accept: application/json' \
--header 'content-type: application/json' \
--data '{
"operation": "cancelOccurrence",
"eventReference": "<eventReference>",
"occurrenceReference": "<occurrenceReference>",
"expectedEventVersion": 1,
"expectedOccurrenceVersion": 1
}'const response = await fetch('${APP_BASE_URL}/calendar/v1/recurrence-commands', {
method: 'POST',
headers: {
authorization: `Bearer ${ACCESS_TOKEN}`,
accept: 'application/json',
'content-type': 'application/json',
},
body: JSON.stringify({
"operation": "cancelOccurrence",
"eventReference": "<eventReference>",
"occurrenceReference": "<occurrenceReference>",
"expectedEventVersion": 1,
"expectedOccurrenceVersion": 1
}),
}
if (!response.ok) throw new Error(`Vision API ${response.status}`)
const result = await response.json()import json
import urllib.parse
import urllib.request
request = urllib.request.Request(
'${APP_BASE_URL}/calendar/v1/recurrence-commands',
data=json.dumps({"operation":"cancelOccurrence","eventReference":"<eventReference>","occurrenceReference":"<occurrenceReference>","expectedEventVersion":1,"expectedOccurrenceVersion":1}).encode(),
headers={
"Accept": "application/json",
"Authorization": "Bearer <ACCESS_TOKEN>",
"Content-Type": "application/json"
},
method='POST',
)
with urllib.request.urlopen(request, timeout=30) as response:
result = json.load(response)The current TypeScript reference client covers Platform token exchange and core reads. No native SDK helper is declared for this operation; use the HTTP contract directly and follow the SDK guidance.
Responses
| Status | Meaning | Schema |
|---|---|---|
| 200 | Occurrence exception recorded | object |
| 400 | Request validation failed | object |
| 401 | Credential missing or invalid | object |
| 403 | Credential lacks entitlement, scope, or active binding | object |
| 404 | No accessible record was found | object |
| 409 | Time conflict, stale record version, invalid state, or idempotency-key conflict | object |
| 503 | Database or required configuration unavailable | object |
Success response schema
| Field | Type | Rules | Description |
|---|---|---|---|
| schemaVersion | "vision-calendar-command-result.v1" | required | Not described in the contract. |
| operation | event.create | event.update | event.cancel | hold.create | hold.release | attendance.respond | recurrence.exception.cancel | recurrence.exception.modify | required | Not described in the contract. |
| outcome | "succeeded" | required | Not described in the contract. |
| publicReference | string | required | Not described in the contract. |
| recordVersion | integer | required; minimum 1 | Not described in the contract. |
| replayed | boolean | required | Not described in the contract. |
{
"schemaVersion": "vision-calendar-command-result.v1",
"operation": "event.create",
"outcome": "succeeded",
"publicReference": "<publicReference>",
"recordVersion": 1,
"replayed": true
}Errors and troubleshooting
Error bodies and codes are shown only where the approved contract declares them. Use status, the declared error schema, and any correlation identifier returned by the App; do not infer that two Apps share one envelope.
400— Request validation failed401— Credential missing or invalid403— Credential lacks entitlement, scope, or active binding404— No accessible record was found409— Time conflict, stale record version, invalid state, or idempotency-key conflict503— Database or required configuration unavailable
Collection behavior
Pagination: not declared. Filtering/search: not declared. Sorting: not declared.
Cursor lifetime, cursor binding, stable ordering, maximum traversal, and unknown-filter behavior are not assumed unless stated by a parameter description or schema constraint above.
Operational behavior
- Rate limit: No operation-specific limit or 429 response is declared.
- Retry: Retry only when the documented error model or response headers authorize it. Timeout and backoff values are not declared by this operation.
- Idempotency: No idempotency header or replay window is declared.
- Concurrency: No ETag, If-Match, or optimistic-version header is declared.
Security and privacy
- Keep client credentials and bearer tokens on trusted servers.
- Send only to the exact approved HTTPS origin and audience.
- Treat response data according to the owning App's classification and retention policy; the OpenAPI contract does not itself grant data access.
- Do not log credentials, tokens, complete private payloads, or secrets.
Edge cases and known documentation gaps
- No detailed operation description.
- No stable operation ID (legacy exception).
- No direct server URL; gateway routing is unresolved here.
- The request body has no purpose or conditional-rule description.
- Business roles, timeout, retry budget, rate value, idempotency window, and concurrency behavior are absent unless explicitly stated above.
Related operations and workflows
- POST /calendar/v1/event-commands — Create, update, or cancel a locally authoritative event
- POST /calendar/v1/attendance-commands — Record the authorized actor's response to an internal invitation
- POST /calendar/v1/hold-commands — Create or release an expiring scheduling hold
Contract history and evidence
- Contract version:
1.6.0 - Approved snapshot SHA-256:
51244aff8a88e7985ddd9b3552be65108b7fab1fe0c81a3b93fda8a5c5e20dab - Approval: Calendar lane (Claude), authorized by Anthony, 2026-08-21T23:03:07.458Z (calendar-readiness-endpoint-20260821)
- Download the authoritative OpenAPI 3.1 snapshot