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.
- 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).
The following is a list of common terms used in this API:
- A file generated by Google 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.
- A session using Meet, or to notify others that a call is beginning or in progress and allow them to immediately join.
- A conference is an instance of a call within a meeting space. Users typically consider this scenario a single meeting.
- 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
namefield of a
- 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 conferences are 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.
- 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.participantsresource 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.participantSessionsresource 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:
|Allow apps to read metadata about any meeting space the user has access to.
|Allow apps to create, modify, and read metadata about meeting spaces created by your app.
|Allow apps to download recording and transcript files from Google Drive API.
For more information about specific OAuth 2.0 scopes, see OAuth 2.0 Scopes for Google APIs.
To learn about developing with Google Workspace APIs, including handling authentication and authorization, refer to Develop on Google Workspace.
To learn how to create a meeting space with Meet REST API, read the Work with meeting spaces guide.