Vision Developers
POST/calendar/v1/people/agenda

Colleagues' time, as each of them shares it

Who can be added, what each person shares, and the time of the people named. A person's own sharing decides what comes back and the caller's role never does: a busy item carries a time and no title or event reference, and busy time that overlaps is one item. A title comes back only when the caller is on the event, or when the person shares details and the event and its calendar aren't kept private. subject is Core's identity for the person, for Core's use.

App
Calendar
Contract
Calendar API 1.20.0
Lifecycle
preview
Runtime
restricted
Operation ID
readPeopleAgenda
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

Colleagues' time, as each of them shares it

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/people/agenda

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:availability:read

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.

FieldTypeRulesDescription
actorReferencesarrayrequired; maximum items 20Not described in the contract.
fromstring · date-timerequiredNot described in the contract.
tostring · date-timerequiredNot 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/people/agenda' \
  --request POST \
  --header 'authorization: Bearer ${ACCESS_TOKEN}' \
  --header 'accept: application/json' \
  --header 'content-type: application/json' \
  --data '{
    "actorReferences": [
      "<actorReferences>"
    ],
    "from": "2026-08-21T18:00:00Z",
    "to": "2026-08-21T18:00:00Z"
  }'
JavaScript (server-side)
const response = await fetch('https://calendar.runonvision.com/calendar/v1/people/agenda', {
  method: 'POST',
  headers: {
    authorization: `Bearer ${ACCESS_TOKEN}`,
    accept: 'application/json',
    'content-type': 'application/json',
  },
  body: JSON.stringify({
  "actorReferences": [
    "<actorReferences>"
  ],
  "from": "2026-08-21T18:00:00Z",
  "to": "2026-08-21T18:00:00Z"
}),
}

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/people/agenda',
    data=json.dumps({"actorReferences":["<actorReferences>"],"from":"2026-08-21T18:00:00Z","to":"2026-08-21T18:00:00Z"}).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

StatusMeaningSchema
200The people and their timeobject
400Invalid request or not authorizedobject

Success response schema

FieldTypeRulesDescription
schemaVersion"vision-calendar-people-agenda.v1"requiredNot described in the contract.
viewerobjectrequiredNot described in the contract.
viewer.actorReferencestringrequiredNot described in the contract.
viewer.sharingbusy | detailsrequiredNot described in the contract.
peoplearrayrequiredNot described in the contract.
itemsarrayrequiredNot described in the contract.
200 illustrative response
{
  "schemaVersion": "vision-calendar-people-agenda.v1",
  "viewer": {
    "actorReference": "<actorReference>",
    "sharing": "busy"
  },
  "people": [
    {
      "actorReference": "<actorReference>",
      "displayName": "<displayName>",
      "sharing": "busy",
      "subject": "<subject>"
    }
  ],
  "items": [
    {
      "reference": "<reference>",
      "actorReference": "<actorReference>",
      "startsAt": "2026-08-21T18:00:00Z",
      "endsAt": "2026-08-21T18:00:00Z",
      "allDay": true,
      "visibility": "busy",
      "title": "<title>"
    }
  ]
}

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 — Invalid request or not authorized

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.

Contract history and evidence