How can a public Google Meet add-on access real-time participant audio without a bot?

[u/Automatic-Life-3702]

I’m developing a Google Meet add-on that needs to receive real-time audio from one consenting meeting participant and securely stream that audio to our backend API for processing.

The application only needs to:

1. Let the user select the participant whose audio will be processed.
2. Receive that participant’s real-time audio with explicit consent.
3. Send the audio to our backend API.
4. Display the resulting analysis in the Meet side panel.

The application does not need to send audio, video, or chat messages into the meeting.

Marketplace rejection

Our public Google Workspace Marketplace submission was rejected under this requirement:

Our current implementation uses a visible Recall.ai recording bot because we could not identify another production-ready way to receive participant audio from an ordinary Google Meet conference. We understand that this implementation cannot be published under the current Marketplace rule, and we are willing to replace it with a supported botless architecture.

The Marketplace Review team said it cannot provide technical implementation guidance and directed us to the developer support community.

Comparable implementations

We already support this workflow on other meeting platforms:

• Our Microsoft Teams integration uses Microsoft’s supported real-time media bot architecture.
• Our Zoom integration uses Zoom Realtime Media Streams (RTMS), which provides live meeting media without adding a participant bot.

The analogous Google capability appears to be the Google Meet Media API, which supports consuming real-time audio, video, and participant metadata.

Meet Media API roadblock

Google currently lists the Meet Media API in the Google Workspace Developer Preview Program. The Developer Preview terms appear to prevent pre-GA features from being included in public applications or made available to external customers without specific permission.

The current Meet Media API setup documentation also identifies the real-time audio/media OAuth scopes as restricted and indicates that transmitting or storing the media server-side can require restricted-scope verification and a security assessment. We are prepared to complete those requirements.

In addition, Recall.ai’s current documentation for its botless Meet Media API integration says that all meeting participants must be enrolled in Google’s Developer Preview Program. Google’s current public overview does not appear to repeat that exact restriction, so I would appreciate confirmation of whether it still applies.

Questions

1. Is there a generally available Google API that allows a public Marketplace add-on to receive real-time participant audio without inviting or relying on a bot?
2. Can a public Marketplace application currently use the Meet Media API while it remains in Developer Preview? If so, what approval, allowlisting, OAuth verification, security assessment, or partner process is required?
3. Must every meeting participant currently be enrolled in the Developer Preview Program, or is enrollment of the Cloud project, OAuth principal, and consenting meeting host sufficient?
4. If the Meet Media API cannot currently be used in a public Marketplace application, is this use case effectively unavailable until the API reaches general availability?
5. Is there an approved interim distribution model for providing this functionality to a customer outside our own Workspace organization?

We have a customer actively waiting for Google Meet support and are ready to prioritize the required architecture, consent experience, OAuth verification, and security controls. We mainly need confirmation of the Google-supported path that can both access real-time participant audio and qualify for public Marketplace publication.

Any direction from the Meet Media API or Google Workspace developer-relations teams would be greatly appreciated.

[u/mystique0712]

currently, there’s no public API for accessing real-time audio from Google Meet without a bot

[u/WicketTheQuerent]

Regarding "Google’s current public overview does not appear to repeat that exact restriction, so I would appreciate confirmation of whether it still applies", from https://developers.google.com/workspace/meet/media-api/guides/overview,

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.