Assigned
Status Update
Comments
jp...@google.com <jp...@google.com> #2
Generated Metadata
- Summary: The Google Meet API v2beta is returning a 403 error when attempting to add a co-host to a meeting space, even when the user is the meeting organizer. The developer is trying to add a co-host from outside the organization.
- Tags:
Additional resources:
https://stackoverflow.com/.../google-meet-update-space-and-add-members-... https://stackoverflow.com/questions/tagged/google-meet https://developers.google.com/workspace/meet/api/guides/overview https://stackoverflow.com/questions/tagged/google-meet?tab=Active https://stackoverflow.com/questions/tagged/google-meet?tab=Votes
You can
bl...@google.com <bl...@google.com> #3
Automated by Blunderbuss job workspace-devrel-public-issue-tracker-blunderbuss-autoassigner for config shared_rate_limited_assign for component 1179975.
Description
Our end goal is to create a meeting with a co-host (outside the organization). We thought that using Google Meet's v2beta, we should be able to add a "member" to the "space" with its Role being COHOST (as described in the doc at
Creating a meeting, adding members, and all works. But, when we try to add the Role, the create member endpoint returns 403.
We tried many solutions, including this one on Stackoverflow (
### Code
POST
{
"name": "John Doe",
"email": "test@test.com",
"role": "COHOST"
}
### Output
{
"error": {
"status": "PERMISSION_DENIED",
"message": "Permission denied on resource Member (or it might not exist)",
"code": 403
}
}
### Steps
1. Create a space.
2. Optional: add a Calendar Event with the space's conferenceId and two participants
3. Try to add one of the participants as a member with Role being COHOST.
### Notes
- We even tried putting "moderation" to "ON" in space config, but that didn't help either.
- Our end goal is to be able to add a person outside our organization as a co-host to our meetings. So, any alternative solution would be much appreciated!