Calendar API
The Calendar API includes eight routes:Connect Your Calendar
oauth_url in a browser and grant read-only calendar access. After the callback succeeds, list the connection to obtain its id and connected status.
Configure Auto-join
Connection defaults apply to sessions adopted after the change; they do not rewrite already-created sessions.
bot_will_join in a meeting response is the effective decision under policy, while bot_will_join_override is the explicit nullable override.
Timing, Ownership, and Identity Retention
Calendar scheduling applies the configured join lead time. Ifevent.start_time - lead_time is still in the future, the bot starts joining then; if that lead window has elapsed, it starts at the event start time rather than using a past join_at.
Calendar connections, settings, and tracked-meeting controls are owned by the user who connected the calendar. Sessions generated from those meetings, and their transcripts, recordings, events, artifacts, and usage data, are organization-level Meeting resources visible to other authenticated users or API keys in the same Telnyx organization.
Organizer and attendee identities are retained only for a configured post-event window (currently 24 hours by default) and are then scrubbed from Calendar meeting records. Disconnecting also erases those Calendar identity fields. This identity-retention boundary does not delete the separately retained organization-level Meeting session resources.
Related
- Join with a meeting URL — create sessions through the API
- Live Transcript — follow the transcript stream in real time
- Collect Results — read the finalized transcript and summary