How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Google Meet Transcripts API

The Transcripts API from Google Meet — 4 operation(s) for transcripts.

Google Meet Transcripts API is one of 5 APIs that Google Meet publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Transcripts. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 4 operations across 4 paths, and defines 2 schemas. It is described by OpenAPI 3.1.0, at version v2.

Requests are made against a single base URL, https://meet.googleapis.com.

4 operations 4 paths 2 schemas 4 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
v2
Base URL
https://meet.googleapis.com/v2
Authentication
OAuth 2.0, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Google Meet Transcripts API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 3 scopes. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

Paths & Operations 4

Across 4 paths, the API surfaces 4 operations — 4 GET. Each is listed below with its method, path, parameters, and response codes.

Transcripts 4
GET
/v2/conferenceRecords/{conferenceRecord}/transcripts
List transcripts for a conference
1 param → 200
GET
/v2/conferenceRecords/{conferenceRecord}/transcripts/{transcript}
Get a transcript
2 params → 200
GET
/v2/conferenceRecords/{conferenceRecord}/transcripts/{transcript}/entries
List transcript entries
2 params → 200
GET
/v2/conferenceRecords/{conferenceRecord}/transcripts/{transcript}/entries/{entry}
Get a transcript entry
3 params → 200

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are TranscriptEntry (6 properties), Transcript (5 properties). Each schema is shown below with its type and property counts.

Transcript
object
5 properties
TranscriptEntry
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

meet-transcripts-api-openapi.yml Raw ↑

Other APIs Google Meet publishes across the network.

Google Meet Conference Records API
Google Meet Participants API
Google Meet Recordings API
Google Meet Spaces API
Where this information came from

This is an independent, third-party profile of Google Meet Transcripts API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.