[null,null,["最終更新日 2025-08-29 UTC。"],[],[],null,["# Google Meet meeting spaces overview\n\nThis guide explains how the Google Meet REST API lets you create and manage meetings\nfor Google Meet.\n\nA [meeting space](/workspace/meet/api/guides/overview#meeting-space) represents\na virtual place or a persistent object (such as a meeting room) where\nconferences are held. Only one active conference can be held in one space at any\ntime. A meeting space also helps users meet and find shared resources.\n\nTo work with meeting spaces, see [Create and manage meeting\nspaces](/workspace/meet/api/guides/meeting-spaces). To learn how to\nprogrammatically configure a meeting space, see [Configure meeting spaces and\nmembers](/workspace/meet/api/guides/meeting-spaces-configuration).\n\nThe following table details the meeting roles required to use the meeting space\nmethods:\n\n| Method | Owners | Participants | Others |\n|------------------------|--------|--------------|--------|\n| `endActiveConference` | x | | |\n| `get` | x | x | x |\n| with settings | x | | |\n| with active conference | x | x | |\n| `patch` | x | | |\n\nAuthenticating and authorizing with [user\ncredentials](/workspace/meet/api/guides/authenticate-authorize) lets\nGoogle Meet apps access user data and perform operations on the authenticated\nuser's behalf. Authenticating with [domain-wide\ndelegation](/workspace/meet/api/guides/authenticate-authorize#domain-wide-delegation)\nlets you authorize an application's service account to access your users' data\nwithout requiring each user to give consent.\n\nHow Meet identifies a meeting space\n-----------------------------------\n\nThe Google Meet REST API generates a\n[`spaces`](/workspace/meet/api/reference/rest/v2/spaces) resource for each\nmeeting space. The `name` field is the resource name for the resource.\n\nThe following are two important ways to identify a meeting space using the\n`name` field:\n\n- `space_id` is the resource identifier for the space, formatted as\n `spaces/{space}`. It's a unique, server-generated ID and is case sensitive.\n For example, `spaces/jQCFfuBOdN5z`.\n\n- `meetingCode` is an alias for the space, formatted as\n `spaces/{meetingCode}`. It's a typeable, unique character string and is\n non-case sensitive. For example, `abc-mnop-xyz`. The maximum length is 128\n characters. It forms part of the `meetingUri`:\n `https://meet.google.com/abc-mnop-xyz`.\n\n | **Note:** A `meetingCode` shouldn't be stored long term as it can become dissociated from a meeting space and can be reused for different meeting spaces in the future. Generally, a `meetingCode` expires 365 days after last use. For more information, see [Learn about meeting codes in\n | Google Meet](https://support.google.com/meet/answer/10710509).\n\nTo manage a meeting space, use the following values for the `{name}` field:\n\n- To get details about a meeting space, you can use either `spaces/{space}` or\n the alias `spaces/{meetingCode}`. For more information, see [Get a meeting\n space](/workspace/meet/api/guides/meeting-spaces#get-meeting-space).\n\n- To update the details of a meeting space, you can only use `spaces/{space}`.\n For more information, see [Update a meeting\n space](/workspace/meet/api/guides/meeting-spaces#update-meeting-space).\n\n- To end an active conference within a meeting space, you can only use\n `spaces/{space}`. For more information, see [End active\n conference](/workspace/meet/api/guides/meeting-spaces#end-active-conference).\n\nRelated topics\n--------------\n\n- [Create and manage meeting spaces](/workspace/meet/api/guides/meeting-spaces)\n- [Configure meeting spaces and members](/workspace/meet/api/guides/meeting-spaces-configuration)"]]
