For the complete documentation index, see llms.txt.

POST /v1/oauth/connect-token

Mint Calendar Connect Token

Create a single-use, short-lived token for initiating calendar OAuth. The token binds the authenticated user's identity and optional redirect URL into a server-side record. It connects the caller's own calendar only. Pass the returned token to `GET /v1/calendars/google/connect` or `GET /v1/calendars/microsoft/connect` as the `token` query parameter. Tokens expire after 5 minutes and are consumed on first use.

Auth required: Yes

Request Body

• provider: string (required) — Calendar provider to connect
• redirect_url: string — Where to redirect after OAuth completion (must be HTTPS)
• principal_id: string — Removed 2026-09-28. Sending it returns `400 principal_id_not_supported`. It let any caller create a connection to any principal. Connect a customer to a business with an invitation or `GET /v1/calendars/google/connect-guest`.
• business_id: string — Removed with `principal_id`; returns `400 principal_id_not_supported`.

Responses

• 201: Connect token created
• 400: Invalid request (bad redirect_url, missing provider, or `principal_id_not_supported`)
• 401: Authentication required or invalid
• 429: Rate limit exceeded (10 requests per minute per user)

Authentication

Requires authentication. Pass a Bearer token (Supabase JWT) or an API key (`Authorization: Bearer vennio_sk_live_*`) in the request headers.

Base URL: https://api.vennio.app