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 conferenceRecords API

The conferenceRecords API from Google Meet — 7 operation(s) for conferencerecords.

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

This API exposes 1 JSON Schema definition.

Tagged areas include Conference Records. The published artifact set on APIs.io includes an OpenAPI specification, a JSON-LD context, and 1 JSON Schema.

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

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

7 operations 7 paths 10 schemas 7 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
Contact
Resource Areas
1

Paths & Operations 7

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

conferenceRecords 7
GET
/v2/conferenceRecords
Google Meet List conference records
listConferenceRecords 3 params → 200
GET
/v2/conferenceRecords/{conferenceRecordId}
Google Meet Get conference record
getConferenceRecord 1 param → 200
GET
/v2/conferenceRecords/{conferenceRecordId}/participants
Google Meet List participants
listParticipants 3 params → 200
GET
/v2/conferenceRecords/{conferenceRecordId}/participants/{participantId}
Google Meet Get participant
getParticipant 2 params → 200
GET
/v2/conferenceRecords/{conferenceRecordId}/recordings
Google Meet List recordings
listRecordings 1 param → 200
GET
/v2/conferenceRecords/{conferenceRecordId}/transcripts
Google Meet List transcripts
listTranscripts 1 param → 200
GET
/v2/conferenceRecords/{conferenceRecordId}/transcripts/{transcriptId}/entries
Google Meet List transcript entries
listTranscriptEntries 2 params → 200

Schemas 10

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

ConferenceRecord
object
5 properties
ListRecordingsResponse
object
2 properties
Recording
object
4 properties
ListParticipantsResponse
object
3 properties
TranscriptEntry
object
6 properties
ListConferenceRecordsResponse
object
2 properties
ListTranscriptsResponse
object
2 properties
Transcript
object
4 properties
Participant
object
3 properties
ListTranscriptEntriesResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

google-meet-conferencerecords-api-openapi.yml Raw ↑

Other APIs Google Meet publishes across the network.

Google Meet Google Meet API API
Google Meet Spaces API
Where this information came from

This is an independent, third-party profile of Google Meet conferenceRecords 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.