Connect a calendar account
Verifies the credential against the provider and, only if it works, stores it encrypted. A credential the provider rejects is a 400 and no connection is created: a connection that has never worked would next be exercised by an inbound call at 2am, with nobody there to fix it.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
Input for connecting a calendar account.
Who holds the calendar. CAL_COM is the only provider that can be connected today; GOOGLE and CALENDLY are described by capabilities but not yet connectable.
CAL_COM, GOOGLE, CALENDLY Customer-facing name for this account, unique within the project. Required.
1 - 120For CAL_COM: a Cal.com API key (starts with cal_). It is verified against Cal.com before anything is stored, so an invalid key is a 400 and no connection is created. Stored encrypted and never returned.
1The named IANA timezone to offer slots in, for example America/Los_Angeles. Omit to adopt the provider account’s own timezone. A fixed offset such as -08:00 is rejected: it does not observe DST.
1Response
The connected calendar.
A project’s credential for one calendar account, the thing a calendar tool books against. The credential itself is never returned.