Unable to add myself as a group admistrator

API and Webhooks
1

I am trying to add myself as an administrator to a group by issuing the following request:

POST https://api.zoom.us/v2/groups/sVUG-<...snip...>/admins

{"members":[{"id":"<... snipped for security reasons ...>"}]}

The response does not indicate that an error occurred:

HTTP/1.1 201 Created

{"ids":"","added_at":"2025-04-01T18:56:01Z"}

but, as you can see, the ids field is blank and in the Zoom interface I can see that I was NOT added as an administrator to this group. What could cause this?

1 Like
2

Hi @desautelsj , can you confirm pre-reqs outlined here are met?

4

I am able to create new groups, update existing group, add members to a group via the API. It’s only adding administrator to a group that doesn’t seem to work. One thing I forgot to mention is that I am able to add myself as the administrator of a group via the Zoom UI.

It’s only when I try to do it from the API that I don’t get the expected result. What’s confusing is that I do not get an error message. All I get is an empty ids field in the response.

5

Hi @desautelsj ,

When you’re adding yourself as an admin from the UI, are you doing so from the account owner?

Is the account owner role the same one who auth the app and is trying to assign admin role for groups via API?

6

Yes. My user is the account owner.

Yes. My user is the only user in my account and I authored the OAuth app using my user.

7

It looks like the request was syntactically correct but semantically failed—Zoom returned a 201 Created without actually adding the admin. The empty "ids" field suggests that the member ID might be invalid, missing, or not eligible (e.g., not part of the group or lacking necessary permissions). Double-check that:

  1. The id you provided is correct and refers to a valid Zoom user.
  2. The user is already a member of the group (required before admin promotion).
  3. You (the requester) have the necessary permissions (e.g., account admin or owner).

Zoom’s API sometimes returns success status codes even if the operation didn’t fully succeed, so also check logs or enable verbose error reporting if available.

1 Like
8

@shoaibshabeer thanks for the suggestions,

I know my user id is correct. I am able to successfully add myself as a regular member of the same group therefore I can say with confidence that the user Id is indeed correct.

hummmm. Are you certain that a user must be a member before they can be added as an administrator? I am not finding any mention of this fact in the API docs. Furthermore, I am able to add an administrator in the UI without adding this person as a member.

I tested it anyway, just to eliminate this possibility:

First, I added myself as a member of a group, like so:

REQUEST:
POST https://api.zoom.us/v2/groups/hr9W2PRcSY2bHQGaDCyPTQ/members
{"members":[{"id":"<...my user id ...>"}]}

RESPONSE:
HTTP/1.1 201 Created
{"ids":"8lzIwvZTSOqjndWPbPqzuA","added_at":"2025-04-05T13:14:07Z"}

As you can see, my user was successfully added as a member.

Secondly, I attempted to “promote” myself to be an administrator of same group, like so:

REQUEST:
POST https://api.zoom.us/v2/groups/hr9W2PRcSY2bHQGaDCyPTQ/admins
{"members":[{"id":"<...my user id...>"}]}

RESPONSE:
HTTP/1.1 201 Created
{"ids":"","added_at":"2025-04-05T13:14:07Z"}

As you can see, I get the same bizarre JSON response where the ids node is empty and the added_at node contains a date.

The API documentation says that you must have either one of the following scopes:

Scopes: group:write:admin
Granular Scopes: group:write:administrator:admin

I verified my OAuth configuration and I can confirm that it has the required scope:

image
image684Ă—358 39.8 KB

What makes this problem diffuclt to investigate is the complete lack of an error message.

2 Likes
9

@gianni.zoom I’m just checking in: are you still investigating? Is there any additional info I can provide to help the investigation.

By the way, here’s a tracking Id in case it could be helpful:

x-zm-trackingid: v=2.0;clid=us06;rid=WEB_77acaca37c25344b173e9390b8402d78
11

Hey @desautelsj ,

Your request body should be:

"admins": [
    {
      "email": "jchill@example.com",
      "id": "v4iyWT1LTfy8QvPG4GTvdg"
    }
  ]
}'
12

oh I see I named the JSON node members instead of admins. I made the correction and I can confirm it solved the problem.

I wish the API returned a more meaningful error message along the lines of Unknown 'members' node, or something similar.

1 Like
13

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.