For the complete documentation index, see llms.txt.

GET /v1/calendars/google/connect-guest

Guest Calendar Connect (Google) — legacy

Deprecated

**Legacy.** Use `POST /v1/calendars/google/connect-guest-link`. This form takes a raw `principal_id` in the URL, so anyone who knows the ID can start a connect. It stays available only for embeds that existed before the link endpoint; other businesses get `410 connect_guest_link_required`. Creates a guest user and redirects to Google OAuth. **Public Endpoint**: No authentication required. **Use Case**: A business's end-customer connects their Google Calendar without needing a Vennio account. The endpoint creates a throwaway guest user, then internally mints a connect token and redirects through the standard token-gated Google OAuth flow. **Security**: `redirect_url` is validated against a hard-coded platform domain allowlist and a per-business `business_redirect_uris` whitelist. External URIs not on either list are rejected with 400. **Result**: when the guest finishes, Vennio creates an active connection between the guest and the business (the connection counts as consent for availability reads) and reports the guest's principal ID two ways: - **Webhook** `consent.granted` to the business, with `grantor_id` (the guest), `grantee_id` (the business), `source: "calendar_connect"`, `connection_id`, `consent_id`, `scopes` and your `reference`. Treat this as the source of truth. - **Redirect**: `redirect_url` gains `google_connected=true`, `principal_id` and `reference`. The URL can be forged by anyone who knows your redirect URL. Confirm the principal against the webhook or `GET /v1/network/connections` before trusting it.

Auth required: No

Parameters

Responses

Authentication

This endpoint does not require authentication.

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