# List user assistants API is giving empty response

**URL:** <https://devforum.zoom.us/t/list-user-assistants-api-is-giving-empty-response/137399>\
**Category:** Users and Groups\
**Created:** [September 16, 2025, 8:30am UTC](https://devforum.zoom.us/t/list-user-assistants-api-is-giving-empty-response/137399 "2025-09-16T08:30:14Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![vijay\_k](https://avatars.discourse-cdn.com/v4/letter/v/96bed5/32.png) [@vijay\_k](https://devforum.zoom.us/u/vijay_k)\
**Post date:** [September 16, 2025, 8:30am UTC](https://devforum.zoom.us/t/list-user-assistants-api-is-giving-empty-response/137399/1 "2025-09-16T08:30:14Z")

</div>

### List user assistants API is giving empty response in spite of assistants available and visible via the Zoom dashboard portal.

API @GetMapping(value = “/users/{hostId}/assistants”)

---

<div class="post-metadata">

**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\
**Post date:** [September 16, 2025, 5:34pm UTC](https://devforum.zoom.us/t/list-user-assistants-api-is-giving-empty-response/137399/2 "2025-09-16T17:34:53Z")

</div>

Hi @vijay_k , [the endpoint](https://developers.zoom.us/docs/api/users/#tag/users/get/users/%7BuserId%7D/assistants) takes the following path parameter:

`userId` The user’s user ID or email address. For user-level apps, pass the `me` value.

Can you confirm your `hostId` is the `userId` ?

---

<div class="post-metadata">

**Author:** ![Mutations](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/mutations/32/50006_2.png) [@Mutations](https://devforum.zoom.us/u/Mutations)\
**Post date:** [September 16, 2025, 6:58pm UTC](https://devforum.zoom.us/t/list-user-assistants-api-is-giving-empty-response/137399/4 "2025-09-16T18:58:52Z")

</div>

@gianni.zoom We are also experiencing the same issue as above and I suspect it’s related to our other thread. Our usage was working for over a year until this past weekend. A `zm-tracking-id` for the GET request: `v=2.0;clid=us06;rid=WEB_40fb99510c1f767107abc58362784d08`

---

<div class="post-metadata">

**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\
**Post date:** [September 16, 2025, 8:43pm UTC](https://devforum.zoom.us/t/list-user-assistants-api-is-giving-empty-response/137399/5 "2025-09-16T20:43:29Z")

</div>

Thanks so much @Mutations , responded in other thread!

---

<div class="post-metadata">

**Author:** ![vijay\_k](https://avatars.discourse-cdn.com/v4/letter/v/96bed5/32.png) [@vijay\_k](https://devforum.zoom.us/u/vijay_k)\
**Post date:** [September 17, 2025, 2:10am UTC](https://devforum.zoom.us/t/list-user-assistants-api-is-giving-empty-response/137399/6 "2025-09-17T02:10:53Z")

</div>

yes, the hostId is the userId (email Id) of the member having zoom license

---

<div class="post-metadata">

**Author:** ![vijay\_k](https://avatars.discourse-cdn.com/v4/letter/v/96bed5/32.png) [@vijay\_k](https://devforum.zoom.us/u/vijay_k)\
**Post date:** [September 17, 2025, 2:46pm UTC](https://devforum.zoom.us/t/list-user-assistants-api-is-giving-empty-response/137399/7 "2025-09-17T14:46:08Z")

</div>

Team,

This is a production issue and we need the resolution at the earliest.

Kindly update us by when this will be fixed?

---

<div class="post-metadata">

**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\
**Post date:** [September 17, 2025, 8:47pm UTC](https://devforum.zoom.us/t/list-user-assistants-api-is-giving-empty-response/137399/8 "2025-09-17T20:47:33Z")

</div>

@vijay_k , please see here:

> [@Zoom API "Add assistants" endpoint stopped working](https://devforum.zoom.us/t/zoom-api-add-assistants-endpoint-stopped-working/137382/10):
>
> @Mutations @Jack7 @Josh13 It turns out that the requests are no longer working with email, but are successful with userId. There’s currently a service engineering ticket open to address this (ZSEE-179683). In the interim, please user userId in the path parameter and request body. You will see when this is fixed to accept user email again in the upcoming changelog.