The Google Meet REST API lets you create and manage meetings for Google Meet and
offers entry points to your users directly from your app.
With the Meet REST API, you can do the following:
- Create a meeting space to connect users over video.
- Get a meeting space or conference by resource name.
- Get a list of participants and participant sessions.
- Get meeting artifacts (recordings, transcripts, and transcript entries).
You can also subscribe to Meet events using the
Google Workspace Events API. To be notified of changes, you can subscribe to a
specified meeting space or to all meeting spaces belonging to a specified user.
For more information, see
Subscribe to events using the
Google Workspace Events API
and
Subscribe to Google Meet
events
.
Use cases
Apps can integrate with the Meet REST API to perform the following tasks:
Before a conference
: Tailor the conference experience as needed by
creating the meeting space. You can also manage invitees and pre-configure
the settings.
During a conference
: Retrieve conference information to change your app
experience based on the metadata returned.
After a conference
: Fetch conference artifacts, such as the recording
and transcription.
Some examples of things you might want to use Meet REST API for include the
following:
Figure 1.
Create and join a dynamic meeting with your colleagues within a Chat space.
You can also incorporate other Google Workspace APIs like Chat API
into your app to take the collaboration even further. For more information, see
Chat use cases
.
Common terms
The following is a list of common terms used in this API:
- Artifact
- A file generated by Meet in response to a
conference
, such as
recordings
and
transcripts
.
Usually an artifact is ready to be fetched soon after a conference ends.
- Calendar event
- An event in Google Calendar with multiple attendees, typically created by a
meeting organizer
, containing the joining info of a meeting.
Meet might be the
conference
solution for the event.
- Call
- A session using Meet, or to notify others that a call is
beginning or in progress and allow them to immediately join.
- Conference
- A conference is an instance of a
call
within a
meeting space
. Users
typically consider this scenario a single meeting.
- Co-host
- A person in a
call
who has been granted host-management privileges by a
host
, except the ability to remove the original host.
- Host
- The person who created a
call
(the
meeting organizer
) or the person who
controls the call. Note that a meeting organizer can organize the meeting
but not be present when it takes place. A host can also delegate host
privileges to a
co-host
.
- Meeting code
- A typeable, unique 10-character string for a
meeting space
used within the
join URL of a meeting space. For example,
abc-mnop-xyz
. Meeting codes
shouldn't be stored long term as they can become dissociated from a meeting
space and can be reused for different meeting spaces in the future.
Generally, meeting codes expire 365 days after last use. For more
information, see
Learn about meeting codes in
Google Meet
.
- Meeting name
- A unique server-generated ID used to identify a
meeting space
. The meeting
ID is returned in the
name
field of a
spaces
resource.
- Meeting organizer
- The user that created the
meeting space
. This user can also be considered
the meeting owner. They might not be present during the
call
or be the
meeting
host
. There can only be one meeting organizer.
- Meeting space
- A virtual place or a persistent object (such as a meeting room) where a
conference
is held. Only one active conference can be held in one space at
any time. A meeting space also helps users meet and find shared resources.
- Participant
- A person joined to a
call
or that uses
Companion
mode
, watching as a
viewer, or a room device connected to a call. There's one
conferenceRecords.participants
resource for each person. When a participant joins the
conference
, a
unique ID is assigned.
- Participant session
- A unique session ID created for each participant-device pair that joins a
call
. There's one
conferenceRecords.participants.participantSessions
resource for each session. If the
participant
joins the same call multiple
times from the same participant-device pair, they're each assigned unique
session IDs.
API-specific authorization and authentication information
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 REST API supports the following OAuth 2.0 scopes:
Scope code
|
Description
|
Usage
|
https://www.googleapis.com/auth/meetings.space.readonly
|
Allow apps to read metadata about any meeting space the user has access to.
|
Sensitive
|
https://www.googleapis.com/auth/meetings.space.created
|
Allow apps to create, modify, and read metadata about meeting spaces created by your app.
|
Sensitive
|
https://www.googleapis.com/auth/drive.readonly
|
Allow apps to download recording and transcript files from Google Drive API.
|
Restricted
|
For more information about specific OAuth 2.0 scopes, see
OAuth 2.0 Scopes for
Google APIs
.