List Calendar connections

This page documents the canonical HTTP contract for this endpoint.

Conditional availability: these routes require CALENDAR_INTEGRATION_ENABLED=true; otherwise they return 404. Use a signed-in user session or a developer API key with the listed Calendar scope. Access uses the key owner’s own connected personal calendar in the current workspace. Calendar OAuth consent is separate from email consent. Credentials are never returned.

A saved connection may report reconnect_required when Calendar consent is missing. An empty list is an account inventory result, not a deployment-wide capability claim.

Command Center reads additionally respect CALENDAR_AGENT_READ_ENABLED; agent writes require CALENDAR_AGENT_ENABLED=true. HTTP and CLI availability do not by themselves prove that the harness adapter is enabled. Use capability discovery for the deployed surface.

Errors

Status	Meaning
400	Invalid range or provider state, reconnect required, CRM match missing, or event not editable.
401	Authentication required.
403	The key lacks the required Calendar scope.
404	Calendar is disabled, the connection is unavailable, or the event is not found.
409	Event version changed; read and review again.
422	Invalid request fields.
502	Calendar provider request failed.

Example

bash

curl -X GET "https://app.autotouch.ai/api/calendar/connections" \
  -H "Authorization: Bearer $AUTOTOUCH_API_KEY"

Response example

json

{
  "connections": [
    {
      "provider": "google",
      "email": "sdr@example.com",
      "status": "connected"
    }
  ]
}