Skip to main content
POST
/
api
/
v1
/
calendars
/
{calendar_id}
/
providers
curl -X POST "https://app.talkover.ai/api/v1/calendars/calendar-uuid-1/providers" \
  -H "Authorization: Bearer talq_your_environment_token_here" \
  -H "Content-Type: application/json" \
  -d '{
    "provider": "calendar_provider_a",
    "redirect_uri": "https://example.com/oauth/calendar/callback"
  }'

{
  "success": true,
  "data": {
    "id": "conn-uuid-1",
    "provider": "calendar_provider_a",
    "authorization_url": "https://provider.example.com/oauth/authorize?...",
    "is_active": false
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.talkover.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
Create Provider Connection

Initiate a connection between a calendar and an external calendar provider. The OAuth flow is completed via a redirect URL returned in the response.

​
Endpoint

POST /api/v1/calendars/{calendar_id}/providers

​
Path Parameters

​
calendar_id
string
required
Calendar UUID.

​
Request Headers

​
Authorization
string
required
Bearer token. Format: Bearer talq_your_environment_token_here
​
Content-Type
string
required
Must be application/json.

​
Request Body

​
provider
string
required
Provider identifier (returned by your environment configuration).
​
redirect_uri
string
required
URL the provider will redirect to after the user authorizes access.

​
Examples

curl -X POST "https://app.talkover.ai/api/v1/calendars/calendar-uuid-1/providers" \
  -H "Authorization: Bearer talq_your_environment_token_here" \
  -H "Content-Type: application/json" \
  -d '{
    "provider": "calendar_provider_a",
    "redirect_uri": "https://example.com/oauth/calendar/callback"
  }'

​
Response

{
  "success": true,
  "data": {
    "id": "conn-uuid-1",
    "provider": "calendar_provider_a",
    "authorization_url": "https://provider.example.com/oauth/authorize?...",
    "is_active": false
  }
}

​
Notes

  • After the user completes the OAuth flow at authorization_url, the connection becomes active and the first sync runs automatically.