[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["没有我需要的信息","missingTheInformationINeed","thumb-down"],["太复杂/步骤太多","tooComplicatedTooManySteps","thumb-down"],["内容需要更新","outOfDate","thumb-down"],["翻译问题","translationIssue","thumb-down"],["示例/代码问题","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-04。"],[],[],null,["# Google Meet REST API overview\n\nThe Google Meet REST API lets you create and manage meetings for Google Meet and\noffers entry points to your users directly from your app.\n\nWith the Meet REST API, you can do the following:\n\n- Create a meeting space to connect users over video.\n- Get a meeting space or conference by resource name.\n- Get a list of participants and participant sessions.\n- Get meeting artifacts (recordings, transcripts, and transcript entries).\n\nYou can also subscribe to Meet events using the\nGoogle Workspace Events API. To be notified of changes, you can subscribe to a\nspecified meeting space or to all meeting spaces belonging to a specified user.\nFor more information, see [Subscribe to events using the\nGoogle Workspace Events API](/workspace/events) and [Subscribe to Google Meet\nevents](/workspace/events/guides/events-meet).\n\nUse cases\n---------\n\nApps can integrate with the Meet REST API to perform the following tasks:\n\n- **Before a conference**: Tailor the conference experience as needed by\n creating the meeting space. You can also manage invitees and pre-configure\n the settings.\n\n- **During a conference**: Retrieve conference information to change your app\n experience based on the metadata returned.\n\n- **After a conference**: Fetch conference artifacts, such as the recording\n and transcription.\n\nSome examples of things you might want to use Meet REST API for include the\nfollowing:\n\n- **Sales and account management**\n\n - Retrieve meeting and participant information for record purposes.\n - Fetch meeting artifacts and post them in accounts.\n - Run transcriptions and recordings through AI models to generate coaching and sales effectiveness analysis.\n- **Learning and development**\n\n - Create and pre-configure meetings for training.\n - Assign co-host roles to trainers and session leads.\n - Retrieve recordings that let students review materials after the course ends.\n- **Developer operations**\n\n - Create meetings to instantly connect teammates.\n - Let other stakeholders join ongoing meetings by sharing real-time meeting and participant information.\n - Run transcription data through AI models to generate the correct next steps.\n\n**Figure 1.** Create and join a dynamic meeting with your colleagues within a Chat space.\n\nYou can also incorporate other Google Workspace APIs like Chat API\ninto your app to take the collaboration even further. For more information, see\n[Chat use cases](/workspace/chat/overview#use-cases).\n| **Note:** The Meet REST API isn't intended for performance tracking or user evaluation within your domain. Meet data shouldn't be collected for this purpose.\n\nCommon terms\n------------\n\nThe following is a list of common terms used in this API:\n\n*Artifact*\n: A file generated by Meet in response to a *conference* , such as\n [`recordings`](/workspace/meet/api/reference/rest/v2/conferenceRecords.recordings) and\n [`transcripts`](/workspace/meet/api/reference/rest/v2/conferenceRecords.transcripts).\n Usually an artifact is ready to be fetched soon after a conference ends.\n\n*Calendar event*\n: An event in Google Calendar with multiple attendees, typically created by a\n *meeting organizer* , containing the joining info of a meeting.\n Meet might be the *conference* solution for the event.\n\n*Call*\n: A session using Meet, or to notify others that a call is\n beginning or in progress and allow them to immediately join.\n\n*Conference*\n: A conference is an instance of a *call* within a *meeting space*. Users\n typically consider this scenario a single meeting.\n\n*Co-host*\n: A person in a *call* who has been granted host-management privileges by a\n *host*, except the ability to remove the original host.\n\n*Host*\n: The person who created a *call* (the *meeting organizer* ) or the person who\n controls the call. Note that a meeting organizer can organize the meeting\n but not be present when it takes place. A host can also delegate host\n privileges to a *co-host*.\n\n*Meeting code*\n\n: A typeable, unique 10-character string for a *meeting space* used within the\n *meeting URI* of a meeting space. It's non-case sensitive. For example,\n `abc-mnop-xyz`. The maximum length is 128 characters.\n\n Meeting codes shouldn't be stored long term as they can become dissociated\n from a meeting space and can be reused for different meeting spaces in the\n future. Generally, meeting codes expire 365 days after last use. For more\n information, see [Learn about meeting codes in\n Google Meet](https://support.google.com/meet/answer/10710509).\n\n*Meeting name*\n\n: A unique server-generated ID used to identify a *meeting space* . It's case\n sensitive. For example, `jQCFfuBOdN5z`. The meeting ID is returned in the\n `name` field of a [`spaces`](/workspace/meet/api/reference/rest/v2/spaces) resource.\n\n*Meeting organizer*\n\n: The user that created the *meeting space* . This user can also be considered\n the meeting owner. They might not be present during the *call* or be the\n meeting *host*. There can only be one meeting organizer.\n\n*Meeting space*\n\n: A virtual place or a persistent object (such as a meeting room) where a\n *conference* is held. Only one active conference can be held in one space at\n any time. A meeting space also helps users meet and find shared resources.\n\n*Meeting URI*\n\n: A clickable URL that starts or joins a user to a *call* . Each call has a\n unique URL consisting of `https://meet.google.com/` followed by the *meeting\n code* . For example, `https://meet.google.com/abc-mnop-xyz`.\n\n*Participant*\n\n: A person joined to a *call* or that uses [Companion\n mode](https://support.google.com/meet/answer/11295507), watching as a\n viewer, or a room device connected to a call. There's one\n [`participants`](/workspace/meet/api/reference/rest/v2/conferenceRecords.participants)\n resource for each person. When a participant joins the *conference*, a\n unique ID is assigned.\n\n*Participant session*\n\n: A unique session ID created for each participant-device pair that joins a\n *call* . There's one\n [`participantSessions`](/workspace/meet/api/reference/rest/v2/conferenceRecords.participants.participantSessions)\n resource for each session. If the *participant* joins the same call multiple\n times from the same participant-device pair, they're each assigned unique\n session IDs.\n\nRelated topics\n--------------\n\n- To learn about developing with Google Workspace APIs, including handling\n authentication and authorization, refer to [Develop on\n Google Workspace](/workspace/guides/getstarted-overview).\n\n- To learn how to create a meeting space with Meet REST API, read the\n [Work with meeting spaces](/workspace/meet/api/guides/meeting-spaces) guide.\n\n- To learn how to subscribe to Google Workspace events, see [Subscribe to\n events using the Google Workspace Events API](/workspace/events)."]]
