Get started with Meet Media API

To use the Google Meet Media API and its associated OAuth scopes, your app must adhere to the following requirements.

Technical requirements

The following constraints are enforced when working with Meet Media API:

Clients must support all of the following codecs:
- AV1
- VP9
- VP8
Clients must use codec implementations compliant with the Meet Media API's codec requirements, including:
- libvpx (Google) to decode VP8 or VP9
- dav1d (VideoLAN) to decode AV1
Clients must support the following WebRTC header extensions:
- Absolute Send Time
- Transport-Wide Congestion Control
- Absolute Capture Time
- Dependency Descriptor
- Audio Level Indication (urn:ietf:params:rtp-hdrext:ssrc-audio-level)
Clients must periodically send a full suite of metrics. For more information, see the client metrics page for details.

For best results and support:

Clients should use the libwebrtc library, and the version should be no more than 12 months behind the latest STABLE Chromium release. Chromium browsers use libwebrtc to implement the WebRTC JavaScript APIs.
Clients should maintain a minimum bandwidth of 4 Mbps.

Codec deprecation policy

Google reserves the right to stop using a codec at any time.
When a new codec is introduced, developers will receive 12 months notice before clients are required to support this codec.

Authentication and authorization

Google Meet Media API clients connect to a conference on behalf of a specific user, using OAuth 2.0 for authentication and authorization.

Appropriate access

Meet Media API scopes

Authorization scopes are the permissions that you request users to authorize for your app to access the meeting content. When someone installs your app, the user is asked to validate these scopes. Generally, you should choose the most narrowly focused scope possible and avoid requesting scopes that your app doesn't require. Users more readily grant access to limited, clearly described scopes.

The Meet Media API supports the following OAuth 2.0 scope:

Scope code	Description	Usage
`https://www.googleapis.com/auth/meetings.conference.media.readonly`	Capture real-time video and audio in Google Meet video calls.	Restricted
`https://www.googleapis.com/auth/meetings.conference.media.audio.readonly`	Capture real-time audio in Google Meet video calls.	Restricted
`https://www.googleapis.com/auth/meetings.conference.media.video.readonly`	Capture real-time video in Google Meet video calls.	Restricted

Due to the sensitive nature of conferences, all Meet Media API scopes are restricted:

Restricted: These scopes provide wide access to Google user data and require you to go through a restricted scope verification process. For information on this requirement, see Google API Services User Data Policy and Additional Requirements for Specific API Scopes. If you store restricted scope data on servers (or transmit), then you must go through a security assessment.

If your app requires access to any other Google APIs, you can add those scopes as well. For more information about Google API scopes, see Using OAuth 2.0 to Access Google APIs.

To define what information is displayed to users and app reviewers, see Configure the OAuth consent screen and choose scopes.

For more information about specific OAuth 2.0 scopes, see OAuth 2.0 Scopes for Google APIs.