Attach or remove a meeting link on an event

Creates the meeting with the EVENT OWNER's connected account: Google Meet (Google event conferenceData), Microsoft Teams (Graph event onlineMeeting), Zoom (meeting create), or stores a custom https link or phone dial-in. Idempotent per event and provider. Calendar keeps the meeting in step afterwards: it moves when the event moves and is cancelled when the event is cancelled. Allowed to the Scheduler service identity. Only the event's organizer may attach or detach a meeting, always on the organizer's own account; a service (the Scheduler) only on a booking it created itself (a CRM booking or an event confirmed from a request hold). Anyone else who can see the event gets 403.

App

Calendar

Contract

Calendar API 1.20.0

Lifecycle

preview

Runtime

restricted

Operation ID

submitConferencingCommand

Canonical origin

https://calendar.runonvision.com

Purpose and use cases

Attach or remove a meeting link on an event

The owning App is Vision Calendar. Calendar owns scheduling resources, workspace and actor bindings, visibility, recurrence, conflict, and concurrency rules.

Request

POST https://calendar.runonvision.com/calendar/v1/sync/conferencing-commands

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:conferencing: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

This operation declares no path or query parameters.

Request body

Media type: application/json. The body is required.

Runnable examples

curl 'https://calendar.runonvision.com/calendar/v1/sync/conferencing-commands' \
  --request POST \
  --header 'authorization: Bearer ***' \
  --header 'accept: application/json' \
  --header 'content-type: application/json' \
  --data '{
    "operation": "attach",
    "eventReference": "<eventReference>",
    "provider": "default",
    "customLinkUrl": "<customLinkUrl>",
    "phoneNumber": "<phoneNumber>",
    "phonePin": "<phonePin>"
  }'

const response = await fetch('https://calendar.runonvision.com/calendar/v1/sync/conferencing-commands', {
  method: 'POST',
  headers: {
  "authorization": "Bearer <ACCESS_TOKEN>",
  "accept": "application/json",
  "content-type": "application/json"
},
  body: JSON.stringify({
  "operation": "attach",
  "eventReference": "<eventReference>",
  "provider": "default",
  "customLinkUrl": "<customLinkUrl>",
  "phoneNumber": "<phoneNumber>",
  "phonePin": "<phonePin>"
}),
})

if (!response.ok) throw new Error(`Vision API ${response.status}`)
const result = await response.json()

import json
import urllib.request

request = urllib.request.Request(
    'https://calendar.runonvision.com/calendar/v1/sync/conferencing-commands',
    data=json.dumps({"operation":"attach","eventReference":"<eventReference>","provider":"default","customLinkUrl":"<customLinkUrl>","phoneNumber":"<phoneNumber>","phonePin":"<phonePin>"}).encode(),
    headers={
    "Authorization": "Bearer <ACCESS_TOKEN>",
    "Accept": "application/json",
    "content-type": "application/json"
},
    method='POST',
)
with urllib.request.urlopen(request, timeout=30) as response:
    result = json.load(response)

curl 'https://calendar.runonvision.com/calendar/v1/sync/conferencing-commands' \
  --request POST \
  --header 'authorization: Bearer ***' \
  --header 'accept: application/json' \
  --header 'content-type: application/json' \
  --data '{
    "operation": "detach",
    "eventReference": "<eventReference>"
  }'

const response = await fetch('https://calendar.runonvision.com/calendar/v1/sync/conferencing-commands', {
  method: 'POST',
  headers: {
  "authorization": "Bearer <ACCESS_TOKEN>",
  "accept": "application/json",
  "content-type": "application/json"
},
  body: JSON.stringify({
  "operation": "detach",
  "eventReference": "<eventReference>"
}),
})

if (!response.ok) throw new Error(`Vision API ${response.status}`)
const result = await response.json()

import json
import urllib.request

request = urllib.request.Request(
    'https://calendar.runonvision.com/calendar/v1/sync/conferencing-commands',
    data=json.dumps({"operation":"detach","eventReference":"<eventReference>"}).encode(),
    headers={
    "Authorization": "Bearer <ACCESS_TOKEN>",
    "Accept": "application/json",
    "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

Success response schema

{
  "schemaVersion": "vision-calendar-conference.v1",
  "conferenceReference": "<conferenceReference>",
  "eventReference": "<eventReference>",
  "provider": "google_meet",
  "status": "active",
  "joinUrl": "<joinUrl>",
  "dialIn": [
    {
      "country": "<country>",
      "number": "<number>",
      "pin": "<pin>"
    }
  ],
  "passcode": "<passcode>",
  "recordVersion": 1
}

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 failed
• 401 — Credential missing or invalid
• 403 — Credential lacks entitlement, scope, or active binding
• 404 — No accessible record was found
• 409 — Time conflict, stale record version, invalid state, or idempotency-key conflict
• 503 — 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

• 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

• GET /calendar/v1/sync/connections — The caller's connected Google, Microsoft and Zoom accounts
• POST /calendar/v1/sync/connection-commands — Connect, choose calendars, resync or disconnect an account
• GET /calendar/v1/sync/ics-subscriptions — The caller's subscribed iCal feeds
• POST /calendar/v1/sync/ics-subscription-commands — Subscribe to, refresh or remove an iCal feed counted as busy time
• GET /calendar/v1/sync/feeds — The caller's private published iCal feeds
• POST /calendar/v1/sync/feed-commands — Create, reset or revoke a private iCal feed link
• GET /calendar/v1/sync/conferencing — The caller's default meeting link and which options are usable now
• POST /calendar/v1/sync/conferencing-preference-commands — Set the caller's default meeting link

Contract history and evidence

• Contract version: 1.20.0
• Approved snapshot SHA-256: ebe491ac249e2cc93315a3ec00300e10f78a28f3ed93d8f232d33320de6e876c
• Approval: Anthony, 2026-11-03T01:23:28.663Z (anthony-docs-live-20261102)
• Download the authoritative OpenAPI 3.1 snapshot