[null,null,["最后更新时间 (UTC)：2025-08-29。"],[],[],null,["# Get started with Meet Media API\n\n| **Developer Preview:** Available as part of the [Google Workspace Developer Preview Program](https://developers.google.com/workspace/preview), which grants early access to certain features. \n|\n| **To use the Meet Media API to access real-time media from a conference, the Google Cloud project, OAuth principal, and all participants in the conference must be enrolled in the Developer Preview Program.**\n\nTo use the Google Meet Media API and its associated OAuth 2.0 scopes, your app must\nadhere to the following requirements.\n\nTechnical requirements\n----------------------\n\nThe following constraints are enforced when working with\nMeet Media API:\n\n- Clients **must** support all of the following codecs:\n\n - `AV1`\n - `VP9`\n - `VP8`\n- Clients **must** use codec implementations compliant with the [Meet Media API's codec\n requirements](/workspace/meet/media-api/guides/codecs), including:\n\n - `libvpx` (Google) to decode `VP8` or `VP9`\n - `dav1d` (VideoLAN) to decode `AV1`\n- Clients **must** support the following WebRTC header extensions:\n\n - [Absolute Send Time](http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time)\n - [Transport-Wide Congestion Control](http://www.ietf.org/id/draft-holmer-rmcat-transport-wide-cc-extensions-01)\n - [Absolute Capture Time](http://www.webrtc.org/experiments/rtp-hdrext/abs-capture-time)\n - [Dependency Descriptor](https://aomediacodec.github.io/av1-rtp-spec/#dependency-descriptor-rtp-header-extension)\n - [Audio Level Indication](https://datatracker.ietf.org/doc/html/rfc6464) (`urn:ietf:params:rtp-hdrext:ssrc-audio-level`)\n- Clients **must** periodically send a full suite of metrics. For more\n information, see the [client metrics](/workspace/meet/media-api/guides/metrics)\n page for details.\n\nFor best results and support:\n\n- Clients **should** use the\n [`libwebrtc`](https://webrtc.googlesource.com/src/) library, and the version\n **should** be no more than **12 months** behind the latest `STABLE` Chromium\n release. Chromium browsers use `libwebrtc` to implement the WebRTC\n JavaScript APIs.\n\n- Clients **should** maintain a minimum bandwidth of **4 Mbps**.\n\n### Enable the Meet REST API\n\nBefore using Google APIs, you need to turn them on in a Google Cloud project. You can turn on one or more APIs in a single Google Cloud project.\n\n- In the Google Cloud console, enable the Google Meet REST API.\n\n [Enable the API](https://console.cloud.google.com/flows/enableapi?apiid=meet.googleapis.com)\n\n### Codec deprecation policy\n\n- Google reserves the right to stop using a codec at any time.\n\n- When a new codec is introduced, developers will receive **12 months notice**\n before clients are required to support this codec.\n\nAuthentication and authorization\n--------------------------------\n\nGoogle Meet Media API clients connect to a conference on behalf of a specific user,\nusing [OAuth 2.0](/identity/protocols/oauth2) for [authentication and\nauthorization](/workspace/guides/auth-overview).\n\n### Appropriate access\n\n| **Important:** See the [Workspace API user data and developer\n| policy](/workspace/workspace-api-user-data-developer-policy#appropriate-access-google-meet-apis) for details about appropriate access to the Google Meet Media API.\n\n### Meet Media API scopes\n\nAuthorization scopes are the permissions that you request users to authorize for\nyour app to access the meeting content. When someone installs your app, the user\nis asked to validate these scopes. Generally, you should choose the most\nnarrowly focused scope possible and avoid requesting scopes that your app\ndoesn't require. Users more readily grant access to limited, clearly described\nscopes.\n\nThe Meet Media API supports the following OAuth 2.0 scope:\n\n| Scope code | Description | Usage |\n|----------------------------------------------------------------------------|---------------------------------------------------------------|------------|\n| `https://www.googleapis.com/auth/meetings.conference.media.readonly` | Capture real-time video and audio in Google Meet video calls. | Restricted |\n| `https://www.googleapis.com/auth/meetings.conference.media.audio.readonly` | Capture real-time audio in Google Meet video calls. | Restricted |\n| `https://www.googleapis.com/auth/meetings.conference.media.video.readonly` | Capture real-time video in Google Meet video calls. | Restricted |\n\nDue to the sensitive nature of conferences, all Meet Media API scopes\nare restricted:\n\n- **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\n Policy](/terms/api-services-user-data-policy) and [Additional Requirements\n for Specific API\n Scopes](/terms/api-services-user-data-policy#additional_requirements_for_specific_api_scopes). If you store restricted scope data on servers (or transmit), then you must go through a security assessment.\n\nIf your app requires access to any other Google APIs, you can add those scopes\nas well. For more information about Google API scopes, see [Using OAuth 2.0 to\nAccess Google APIs](/accounts/docs/OAuth2).\n\nTo define what information is displayed to users and app reviewers, see\n[Configure the OAuth consent screen and choose\nscopes](/workspace/guides/configure-oauth-consent).\n\nFor more information about specific OAuth 2.0 scopes, see [OAuth 2.0 Scopes for\nGoogle APIs](/identity/protocols/oauth2/scopes).\n\nEnd user requirements\n---------------------\n\nIn order to use the Meet Media API, Meet participants must also meet some minimal requirements in order for the conference to be eligible.\n\n### Mobile app versions\n\nFor mobile users, they must update to these versions:\n\n| Platform | App | Version |\n|----------|-----------|------------|\n| Android | Meet app | 309 |\n| iOS | Meet app | 308 |\n| Android | Gmail app | 2025.05.30 |\n| iOS | Gmail app | 6.0.250518 |\n\n### Unsupported platforms\n\nWe don't support third-party hardware clients that run Meet. For example, if your\nend users are using a Cisco hardware conference room device that runs Meet, your Meet Media API instance cannot join the call.\n\n### Age restrictions\n\nMeet Media API is restricted from collecting media from accounts that are registered to minors.\n\nThese are usually accounts that are under age of consent in their respective country (typically under 18 years of age) or were under the age of consent when the account was created by a parent in the [Google Family Link](https://play.google.com/store/apps/details?id=com.google.android.apps.kids.familylink) application.\n\nNote that some regions (such as the EU) have [additional restrictions](https://support.google.com/accounts/answer/1350409) on what kind of accounts are considered under age.\n\nRelated topics\n--------------\n\n- [Meet Media API concepts](/workspace/meet/media-api/guides/concepts)\n\n- [Learn about authentication and authorization](/workspace/guides/auth-overview)\n\n- [Authentication methods at Google](https://cloud.google.com/docs/authentication)"]]
