Overview
Removes a calendar connection for a specific user. This revokes your platform’s access to their calendar and sends auser.calendar.disconnected webhook to all platforms that had this user connected.
Authentication
Requires Platform API Key in theAuthorization header or X-API-Key header.
Request
Path Parameters
Email address of the user whose calendar connection should be removed (URL-encoded)Example:
alice@example.com → alice%40example.comResponse
Success Response (200 OK)
Response Fields
Whether the disconnection succeeded
Human-readable success message
Email of the disconnected user
Your platform’s ID
Multi-Platform Webhook Behavior
IMPORTANT: When a user is disconnected, theuser.calendar.disconnected webhook is sent to ALL platforms that had this user connected, not just your platform.
Example Scenario
-
alice@example.comis connected to 3 platforms:- Boardy (plat_boardy)
- Luma (plat_luma)
- Cal.com (plat_calcom)
-
Boardy calls
DELETE /v1/calendars/alice@example.com -
ALL 3 platforms receive the
user.calendar.disconnectedwebhook:
Example
Use Cases
User Privacy Request
Allow users to revoke calendar access:Account Deletion
Disconnect calendar when user deletes their account:Administrative Removal
Platform admin removes a problematic user:Notes
- This action cannot be undone
- User must reconnect via OAuth to restore access
- Existing scheduled meetings are NOT automatically cancelled
- OAuth tokens are permanently revoked
- All platforms receive the disconnection webhook
Webhook Notification
When a calendar is disconnected, Syncline sends auser.calendar.disconnected webhook to all platforms:
user_requested- User explicitly disconnectedtoken_expired- OAuth token could not be refreshedrevoked- User revoked access from Google
Error Responses
Invalid or missing API key
No calendar connection found for this user and platform
Failed to disconnect calendar
Related Endpoints
List Calendars
View all connected calendars
Platform OAuth URL
Get reconnection URL for users