Broker a WebRTC connection to the active conference of a space.
On success, clients must use the resulting SDP (Session Description Protocol) answer to establish a WebRTC connection. Once connected, additional functionality is available across WebRTC data channels.
HTTP request
POST https://meet.googleapis.com/v2beta/{name=spaces/*}:connectActiveConference
The URL uses gRPC Transcoding syntax.
Path parameters
| Parameters | |
|---|---|
name
|
Required. Resource name of the space. Format: spaces/{spaceId} |
Request body
The request body contains data with the following structure:
| JSON representation |
|---|
{ "offer" : string } |
| Fields | |
|---|---|
offer
|
Required. WebRTC SDP (Session Description Protocol) offer from the client. The format is defined by RFC 8866 with mandatory keys defined by RFC 8829 . This is the standard SDP format generated by a peer connection's createOffer() and createAnswer() methods. |
Response body
Response of spaces.connectActiveConference method.
A success response does not indicate the meeting is fully joined; further communication must occur across WebRTC.
If successful, the response body contains data with the following structure:
| JSON representation |
|---|
{ "answer" : string , "traceId" : string } |
| Fields | |
|---|---|
answer
|
WebRTC SDP answer to the offer. |
traceId
|
Trace ID for debugging purposes. Please include this value when filing bugs. |
Authorization scopes
Requires one of the following OAuth scopes:
-
https://www.googleapis.com/auth/meetings.conference.media.readonly -
https://www.googleapis.com/auth/meetings.conference.media.audio.readonly -
https://www.googleapis.com/auth/meetings.conference.media.video.readonly
For more information, see the OAuth 2.0 Overview .
