Google Meet REST API
Create Meet links and rooms, set access and moderation, end calls, and read attendance, recordings, transcripts and smart notes.
CommunicationGuided#video#meetings#google-meet#google-workspace#transcripts#oauth2
Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.
Overview
The Google Meet REST API lets an app create Meet meeting rooms (spaces) and get their links, control who can join and how the meeting is moderated, end calls, and, after a meeting, read who attended and fetch its recordings, transcripts (with per-speaker entries) and smart notes. Typical uses: instant meeting links in a support, sales or telehealth app; attendance reports; meeting summaries built from transcripts. It does not schedule meetings on calendars: for a meeting with invitations and a Meet link, use the Google Calendar API (see that guided collection). This guided collection covers the core calls; the generated Meet listing on the Google page has every endpoint.
Get credentials, step by step
- Create or pick a project in the Google Cloud console.
- Enable the Google Meet REST API.
- Configure the OAuth consent screen in Google Auth Platform: External (or Internal for a Workspace-only app), publishing status Testing, and add your account as a test user.
- Create an OAuth client under Clients (Desktop app or Web application) and copy the ID and secret into the collection.
- Get a token with the OAuth 2.0 Playground or with folder 1 (sign-in URL, then code exchange).
Authentication and scopes
All calls use Authorization: Bearer <user access token> (service accounts work only with Workspace domain-wide delegation). Scopes:
meetings.space.created(sensitive): create and manage spaces your app created, and read their conference data.meetings.space.readonly(sensitive): read any meeting the user can access, including ones from Calendar or the Meet app.meetings.space.settings(non-sensitive): change settings of all the user's calls; required for automatic recording, transcripts and smart notes.
Sensitive scopes need Google's app verification before a public launch; in Testing mode your test users can use them now (refresh tokens expire after 7 days). Downloading recordings and transcript files goes through the Drive API with restricted Drive scopes. Details: Meet API scopes.
Base URL
https://meet.googleapis.com/v2 ({{baseUrl}}). Resources are addressed by name: spaces/{space}, conferenceRecords/{record}/participants/{participant} and so on; the collection stores the full names and uses them as paths.
How to use this collection
Fill the OAuth variables and get a token, create a space, join its link for a short call, then read the conference record, participants and artifacts. Artifacts appear only if recording, transcription or smart notes ran, which depends on the organizer's Google Workspace edition and admin settings. Conference records and transcript entries are deleted 30 days after a meeting ends, so copy what you need.
Limits
Requests are subject to per-project and per-user rate limits; exceeding them returns 429 (too many requests); creating spaces has a lower limit than other writes. Retry with exponential backoff. There is no daily cap. Current values: Usage limits.
Common errors
| Status | Typical reason | What to do |
|---|---|---|
401 | Invalid Credentials / UNAUTHENTICATED: token missing, expired (about an hour) or revoked | Run Refresh the access token; if that returns invalid_grant, sign in again |
403 | insufficientPermissions / ACCESS_TOKEN_SCOPE_INSUFFICIENT: the token lacks the scope this request needs | Sign in again with the scope listed on the request; check with tokeninfo |
403 | accessNotConfigured / SERVICE_DISABLED: the API is not enabled in this Cloud project | Enable it in the API Library, wait a few minutes |
403 / 429 | rateLimitExceeded, userRateLimitExceeded, RESOURCE_EXHAUSTED: per-user or per-project quota | Back off exponentially and retry; spread work over time |
404 | notFound: wrong ID, or the item belongs to another user / was deleted | Re-run the list request that stores the ID |
400 | invalid / badRequest / INVALID_ARGUMENT: malformed body or parameter | Read error.message; it names the field |
Links
Endpoints 23
1. Get an access token
- POSTExchange the authorization code for tokens
https://oauth2.googleapis.com/tokenSwaps the one-time code from the browser redirect for an access token (about an hour) and a refresh token (long-lived; 7 days while the app is in Testing).… - POSTRefresh the access token
https://oauth2.googleapis.com/tokenGets a fresh access token from the stored refresh token, without the user signing in again. When: whenever a call returns 401 (access tokens last about an… - GETCheck which scopes the token has (tokeninfo)
https://oauth2.googleapis.com/tokeninfoAsks Google what the current access token is good for: the granted scope list, the client it belongs to (aud/azp) and the seconds left (expires_in). When: a…
2. Meeting spaces
- POSTCreate a meeting space
/spacesCreates a new meeting space owned by the signed-in user and returns its join link. When: you need an instant or ad-hoc Meet link (support calls, telehealth… - GETGet a space
/{{spaceName}}Reads a space: its link, settings, and whether a conference is running right now. When: before joining or managing a meeting, or to check if anyone is in it… - GETGet a space by meeting code
/spaces/{{meetingCode}}Looks up a space by its meeting code (abc-mnop-xyz) instead of its ID. The code works as an alias: spaces/abc-mnop-xyz. When: you only have a Meet link, for… - PATCHUpdate space settings (access and moderation)
/{{spaceName}}Changes the settings of a space your app created: here it restricts access to invitees and turns on host moderation with hosts-only chat. When: before a… - PATCHTurn on auto transcripts and smart notes
/{{spaceName}}Sets the space to start transcription and smart notes automatically when the meeting begins (recording works the same way with… - POSTAdd a co-host
/{{spaceName}}/membersAdds a member to the space with a role. Members can join without knocking; the COHOST role can manage most of the meeting (but cannot change auto artifacts or… - GETList space members
/{{spaceName}}/membersLists the members (people with an assigned role) of a space. When: to show who are co-hosts, or before changing roles (PATCH .../members/{member}) or removing… - POSTEnd the active conference
/{{spaceName}}:endActiveConferenceEnds the call currently running in the space: everyone is removed, and a new conference starts the next time someone joins the same link. When: closing a…
3. Conference records and participants
- GETList conference records
/conferenceRecordsLists the user's conference records, newest first. When: finding the record of a meeting to fetch its attendance or artifacts. Scope: meetings.space.readonly… - GETGet a conference record
/{{conferenceRecordName}}Fetches one conference record. When: you already have its name (from List conference records or activeConference in Get a space) and want its times. Scope:… - GETList participants
/{{conferenceRecordName}}/participantsLists everyone who joined the conference, once per person (or room device). When: attendance: who came, first join and last leave time. Scope:… - GETGet a participant
/{{participantName}}Fetches one participant of a conference. When: refreshing one attendee's times, e.g. to see if latestEndTime is still empty (still in the call). Scope:… - GETList participant sessions
/{{participantName}}/participantSessionsLists each separate join of one participant: a new session starts every time the same person and device joins again (for example after a dropped connection).…
4. Recordings, transcripts and smart notes
- GETList recordings
/{{conferenceRecordName}}/recordingsLists the recordings of a conference. When: after the call, to find the MP4 in Drive. Scope: meetings.space.readonly or meetings.space.created. What comes… - GETGet a recording
/{{recordingName}}Fetches one recording, for example to poll until its state becomes FILE_GENERATED. When: after List recordings (uses {{recordingName}}). Scope:… - GETList transcripts
/{{conferenceRecordName}}/transcriptsLists the transcripts of a conference (one per transcription session; stopping and restarting transcription makes a new one). When: after a call that had… - GETGet a transcript
/{{transcriptName}}Fetches one transcript and its state. When: polling until state is FILE_GENERATED, or to get the Docs ID. Scope: meetings.space.readonly or… - GETList transcript entries (who said what)
/{{transcriptName}}/entriesReturns the transcript as structured entries: one per stretch of speech, with the speaker and timestamps. Easier to process than the Docs file (no parsing),… - GETList smart notes
/{{conferenceRecordName}}/smartNotesLists the smart notes (automatically generated meeting notes saved as a Google Doc) of a conference, oldest first. When: after a call with smart notes on.… - GETGet a smart note
/{{smartNoteName}}Fetches one smart notes resource and its state. When: polling until state is FILE_GENERATED, then export the Doc through the Drive API. Scope:…
API details
- Base URL
https://meet.googleapis.com/v2https://oauth2.googleapis.com- Authentication
- A bearer token in the Authorization header
OAuth 2.0 (authorization code flow) - Operations
- 23 operations on 23 pathsGET 16POST 5PATCH 2
- Main resources
- 1. Get an access token 32. Meeting spaces 83. Conference records and participants 54. Recordings, transcripts and smart notes 7
- Description format
- Swastik Codes guided collection, API version
checked against the docs on 2026-11-17 - Links
- Documentation
How to test the Google Meet REST API in Swastik Codes
- Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
- Fork it into your workspaceChoose a workspace. You get your own copy of the Google Meet REST API collection, without the publisher's secrets.
- Add your credentialsThis API uses A bearer token in the Authorization header. Add yours in the collection's variables or an environment; the requests already reference it.
- Send a requestPick an endpoint, for example “Exchange the authorization code for tokens” (POST https://oauth2.googleapis.com/token), and press Send. Check the response, add tests and run the whole collection with the runner.
Frequently asked questions
What is the Google Meet REST API?
Create Meet links and rooms, set access and moderation, end calls, and read attendance, recordings, transcripts and smart notes. It is listed under Communication and has 23 endpoints.
Who publishes the Google Meet REST API?
It is listed from Google's public API description (an OpenAPI document), not published by Google on Swastik Codes. Anyone who controls googleapis.com can claim the profile by adding a DNS TXT record.
What is the base URL of the Google Meet REST API?
Its description lists 2 base URLs: https://meet.googleapis.com/v2, https://oauth2.googleapis.com. The first is the usual one; the others are typically sandbox or regional servers.
How do I authenticate with the Google Meet REST API?
It accepts 2 methods: A bearer token in the Authorization header; OAuth 2.0 (authorization code flow).
How many endpoints does the Google Meet REST API have?
23 operations on 23 paths (16 GET, 5 POST, 2 PATCH). The largest groups are 1. Get an access token, 2. Meeting spaces, 3. Conference records and participants, 4. Recordings, transcripts and smart notes.
Is forking the Google Meet REST API free?
Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.