Connect a calendar system
Stores the credential for a calendar system that is connected by pasting one, such as Cal.com.
The key is not checked against the product here. A key that is right today and revoked tomorrow reads the same, so the connection is proven where it is used rather than at the moment it is saved.
A reconnect replaces the whole connection. Whatever was registered under the old credential is removed first, while that credential can still authenticate the removal; otherwise it stays live in the customer’s account and every cancellation arrives twice.
Registering for cancellations happens here, at connect time, so a connection made before that existed has to be reconnected or backfilled to receive them.
A system that declares itself beta refuses everyone but staff.
Cookie-auth callers must send the x-csrf-token header.
Required API key scope: projects:write.
Authorizations
Send your API key as Authorization: Bearer YOUR_API_KEY.
Path Parameters
The calendar system, lower case.
1Query Parameters
The sub-account this calendar belongs to. It is the only thing that identifies the tenant here, and access is re-checked against it on every call.
Body
The credential.
