AI-generated Key Takeaways
-
Only bots owned by the caller are removed from the meeting.
-
The request uses a POST method with the conference code in the URL.
-
The request body must be empty.
-
The response body may contain a list of error messages if bot removal fails.
-
Authorization requires the
https://www.googleapis.com/auth/meetingsOAuth scope.
Removes all bots from a conference.
Only bots owned by the caller will be removed from the meeting.
HTTP request
POST https://botsondemand.googleapis.com/v1/removeAllBotsFromConference/{conferenceCode}
The URL uses gRPC Transcoding syntax.
Path parameters
| Parameters | |
|---|---|
conferenceCode |
Required. The conference to remove bots from. |
Request body
The request body must be empty.
Response body
Response for {@link RemoveAllBotsFromConferenceRequest}
If successful, the response body contains data with the following structure:
| JSON representation |
|---|
{ "errorMessages": [ string ] } |
| Fields | |
|---|---|
errorMessages[] |
The error messages returned by bot removal failures. |
Authorization scopes
Requires the following OAuth scope:
https://www.googleapis.com/auth/meetings
For more information, see the OAuth 2.0 Overview.