Read meetings through a scoped public API
API endpoints and configurable access keys provided a foundation for integrations.
Read MarkdownDates describe development history and do not verify when changes became available.
Development period: to
Read a meeting list or an individual meeting
addedapiAvailability: unverified
Added API-key-authenticated endpoints for listing meetings and reading an individual meeting’s details.
Both operations required the key’s meeting-read permission and worked within the key’s workspace context.
Choose a key’s read permissions and expiry
addedapiAvailability: unverified
Owners and admins could name an API key, choose its read permissions and set an expiry.
The creation form offered permissions for meetings, transcripts and recordings, with expiration choices of 30, 90 or 365 days, or no expiration.