Install & Compatibility
Where this runs
tested against v0.5.0 · pip install
no network on importno background threads
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
muslpy 3.10–3.910 runs
installs and imports cleanly · install 0.0s · import 1.909s · 70.3MB
glibcpy 3.10–3.910 runs
installs and imports cleanly · install 5.5s · import 1.467s · 68MB
69MB installed
● package 69MB
Code
Verified usage
Verified import paths — ran on the pinned version, not inferred.
SpacesServiceClient
✓ from google.apps.meet_v2beta import SpacesServiceClient
✗ from google.apps.meet import MeetServiceClient
The Meet API is currently exposed via the 'v2beta' client for Spaces, not a generic 'meet' or 'v1' client.
Space
✓ from google.apps.meet_v2beta.types import Space
Type hints and client methods often require importing specific type definitions from the 'types' submodule.
This quickstart demonstrates how to initialize the `SpacesServiceClient` and create a new Google Meet space using default settings. Ensure your environment is authenticated with Google Cloud credentials before running.
import os
from google.apps.meet_v2beta import SpacesServiceClient
from google.apps.meet_v2beta.types import Space
# --- Authentication Setup ---
# The client library automatically looks for credentials in the following order:
# 1. The GOOGLE_APPLICATION_CREDENTIALS environment variable.
# 2. Credentials from `gcloud auth application-default login`.
# 3. Credentials from the Google Cloud SDK (e.g., from `gcloud auth login`).
# For local development, set GOOGLE_APPLICATION_CREDENTIALS or use `gcloud auth application-default login`.
# Example: export GOOGLE_APPLICATION_CREDENTIALS="/path/to/your/keyfile.json"
# Initialize the client
client = SpacesServiceClient()
# Create a new Google Meet space
# An empty Space object is often sufficient for creation, letting the API fill in defaults.
# For advanced configuration, populate the Space object with a SpaceConfig.
new_space = Space()
try:
created_space = client.create_space(space=new_space)
print(f"Successfully created Meet Space.")
print(f"Space Name: {created_space.name}")
print(f"Meeting URI: {created_space.meeting_uri}")
except Exception as e:
print(f"An error occurred: {e}")
if "credentials" in str(e) or "Permission denied" in str(e):
print("Hint: Check your authentication setup and IAM permissions (e.g., 'Google Meet Admin SDK' role).")
Debug
Known issues
gotchaAuthentication is mandatory for all Google Meet API calls. The client library defaults to using Application Default Credentials (ADC).fixEnsure `GOOGLE_APPLICATION_CREDENTIALS` environment variable points to a service account key file, or run `gcloud auth application-default login` for user credentials. Verify the service account or user has the necessary 'Google Meet' API roles (e.g., Google Meet Admin SDK role) on the relevant project/resource.
affects: All versions
gotchaThe primary client for Google Meet is currently `SpacesServiceClient` found under the `v2beta` API version. Other versions or a generic `MeetServiceClient` may not exist or function as expected.fixAlways import from `google.apps.meet_v2beta`, e.g., `from google.apps.meet_v2beta import SpacesServiceClient`.
affects: All versions up to 0.4.0
gotchaWhen making API calls that require a resource name (e.g., retrieving a specific space), ensure the name is in the correct format (`spaces/SPACE_ID`).fixRefer to the Google Meet API documentation for the exact resource name format. A space name will typically be formatted as 'spaces/AAAA-BBBB-CCCC'.
affects: All versions
Errors
Common errors & fixes
ImportError: cannot import name 'SpacesServiceClient' from 'google.apps.meet'
Attempting to import the client from an incorrect or non-existent package path.
fixThe correct import path for the client is `from google.apps.meet_v2beta import SpacesServiceClient`.
google.auth.exceptions.DefaultCredentialsError: Could not automatically determine credentials.
The client library could not find valid Google Cloud credentials in the environment or could not infer them.
fixSet the `GOOGLE_APPLICATION_CREDENTIALS` environment variable to your service account key file path or authenticate using `gcloud auth application-default login`.
403 Permission denied: The caller does not have permission
The authenticated principal (service account or user) lacks the necessary IAM permissions to perform the requested Meet API operation.
fixGrant the required roles to your service account or user. For creating spaces, roles like 'Google Meet Admin SDK' or 'Owner' might be needed on the relevant project, or specific delegated permissions.
Upgrade
Version history
0.5.0latest on PyPI · released Jun 3, 2026
Audit
Dependencies
No dependency data recorded yet.