# Read meetings through a scoped public API

API endpoints and configurable access keys provided a foundation for integrations\.

- Schema version: 1
- ID: meetso\-2026\-05\-05
- Slug: 2026\-05\-05\-read\-meetings\-through\-the\-public\-api\-choose\-api\-key\-permissions\-and\-expiry
- Period: 2026-05-05 to 2026-05-05
- Published: 2026-05-05
- Updated: None
- History: Development history
- Tags: integration

Dates describe development history and do not verify when changes became available.

- Banner asset: api\-access
- Banner alt: A key connected to a bounded section of an interface

![A key connected to a bounded section of an interface](/_next/static/media/api-access.44n5qjxtvr45h.svg)

## Read a meeting list or an individual meeting

- ID: read\-meetings\-through\-the\-public\-api
- Type: added
- Area: api
- Availability: 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

- ID: choose\-api\-key\-permissions\-and\-expiry
- Type: added
- Area: api
- Availability: 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\.