Vision Developers
POST/calendar/v1/sync/oauth/start

Confirm connecting an account (the interstitial's form)

Public. Requires the view cookie set by the interstitial in this browser. Consumes the handoff, sets an HttpOnly cookie scoped to the OAuth path, mints the OAuth state and redirects to the provider with an S256 code challenge.

App
Calendar
Contract
Calendar API 1.20.0
Lifecycle
preview
Runtime
restricted
Operation ID
confirmSyncOAuth
Canonical origin
https://calendar.runonvision.com

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

Confirm connecting an account (the interstitial's form)

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/oauth/start

Authentication and authorization

No authentication requirement is declared for this operation.

Headers

  • Accept: application/json — recommended where a JSON response is declared.
  • Content-Type: application/x-www-form-urlencoded — 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/x-www-form-urlencoded. The body is required.

FieldTypeRulesDescription
handoffstringrequired; maximum length 200Not described in the contract.

Runnable 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
curl 'https://calendar.runonvision.com/calendar/v1/sync/oauth/start' \
  --request POST \
  --header 'accept: application/json' \
  --header 'content-type: application/x-www-form-urlencoded' \
  --data-urlencode 'handoff=<handoff>'
JavaScript (server-side)
const response = await fetch('https://calendar.runonvision.com/calendar/v1/sync/oauth/start', {
  method: 'POST',
  headers: {
    accept: 'application/json',
    'content-type': 'application/x-www-form-urlencoded',
  },
  body: new URLSearchParams({
  "handoff": "<handoff>"
}),
}

if (!response.ok) throw new Error(`Vision API ${response.status}`)
const result = await response.json()
Python 3 standard library
import json
import urllib.parse
import urllib.request

request = urllib.request.Request(
    'https://calendar.runonvision.com/calendar/v1/sync/oauth/start',
    data=urllib.parse.urlencode({"handoff":"<handoff>"}).encode(),
    headers={
    "Accept": "application/json",
    "Content-Type": "application/x-www-form-urlencoded"
},
    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

StatusMeaningSchema
303Redirect to the providernot specified
410The link expired, was already used, or this browser did not open it.string

Success response schema

No schema is declared.

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.

  • 303 — Redirect to the provider
  • 410 — The link expired, was already used, or this browser did not open it.

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.
  • No machine-readable success schema.
  • Business roles, timeout, retry budget, rate value, idempotency window, and concurrency behavior are absent unless explicitly stated above.

Contract history and evidence