Google Meet REST API overview

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 and configure meeting spaces to connect users over video.
  • Pre-configure space access levels, moderation settings, and automatic recordings or transcripts.
  • Manage meeting space members and assign co-host roles.
  • End an active conference programmatically within a meeting space.
  • Get conference records, attendance details, and participant session metadata.
  • Retrieve 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:

Use cases

Apps can integrate with the Meet REST API to perform the following tasks:

  • Before a conference: Create meeting spaces on demand, pre-configure access restrictions (open, trusted, or restricted), apply moderation controls (screen sharing, chat, reactions, microphone, and camera), configure auto-recording or auto-transcription, and assign space members with co-host roles.

  • During a conference: Retrieve active conference metadata and participant sessions, manage members dynamically, listen for real-time lifecycle events using the Google Workspace Events API, or programmatically end the active conference.

  • After a conference: Retrieve conference records and attendance logs, download recordings and Google Docs transcripts from Google Drive, and access granular transcript speech entries for coaching, compliance, or AI analysis.

Some examples of things you might want to use Meet REST API for include the following:

  • Sales and account management

    • Retrieve meeting and participant information for record purposes.
    • Fetch meeting artifacts and post them in accounts.
    • Run transcriptions and recordings through AI models to generate coaching and sales effectiveness analysis.

  • Learning and development

    • Create and pre-configure meetings for training.
    • Assign co-host roles to trainers and session leads.
    • Retrieve recordings that let students review materials after the course ends.

  • Customer support and consulting

    • Create secure, restricted meeting spaces directly from help-desk tickets or client portals.
    • Pre-configure host management so only support agents can present or manage attendance.
    • Enable automatic recording or transcription for quality assurance and compliance records.
    • Programmatically end active conferences when appointments or support sessions conclude.

  • Developer operations

    • Create meetings to instantly connect teammates.
    • Let other stakeholders join ongoing meetings by sharing real-time meeting and participant information.
    • Run transcription data through AI models to generate the correct next steps.
Create and join a dynamic meeting with your colleagues within a Chat space.
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:

Active conference
The ongoing conference taking place inside a meeting space. Only one active conference can be held in a meeting space at any given time. Once ended, it becomes a historical conference record.
Artifact
A file generated by Meet in response to a conference, such as recordings and transcripts. Artifacts are saved to the meeting organizer's Drive. They're usually 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.
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.
Conference
A conference is an instance of a call within a meeting space. Users typically consider this scenario a single meeting.
Conference record
A unique ID for each instance of a conference. It's created automatically when the conference starts. The conferenceRecords resource uses the format conferenceRecords/{conferenceRecord}. For example, conferenceRecords/kRyYx8b7vNDsLpR1tG_cNjFUQBoBRhHIMoGJAJkBCQ.
Dial in
To use a phone to take part in a call or to listen to a streamed call.
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 meeting URI of a meeting space. It's non-case sensitive. For example, abc-mnop-xyz. The maximum length is 128 characters.

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. It's case sensitive. For example, jQCFfuBOdN5z. The meeting ID is returned in the name field of a spaces resource. For more information, see How Meet identifies a meeting space.

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.

Meeting URI

A clickable URL that starts or joins a user to a call. Each call has a unique URL consisting of https://meet.google.com/ followed by the meeting code. For example, https://meet.google.com/abc-mnop-xyz.

Member

A user explicitly added to a meeting space with a designated role (such as COHOST). Unlike a participant who is present only during a live conference, a member is associated with the persistent meeting space and retains their privileges across multiple conferences in that space.

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 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 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.

Recording

An MP4 video file and associated metadata generated when a conference is recorded. Recordings are saved to the meeting organizer's Drive and can be retrieved as meeting artifacts.

SIP address

A Session Initiation Protocol (SIP) address details how third-party video conferencing hardware can find and join a Meet conference. Meet supports the SIP URI scheme.

Transcript

A text document capturing the spoken conversation from a conference, exported to the meeting organizer's Drive as a Docs file.

Transcript entry

A discrete segment of transcribed speech from a participant in a conference. Each entry includes the participant identity, timestamp, spoken text, and language code, and is available for 30 days after the conference ends.