# Zoom API "Add assistants" endpoint stopped working

**URL:** <https://devforum.zoom.us/t/zoom-api-add-assistants-endpoint-stopped-working/137382>\
**Category:** API and Webhooks\
**Created:** [September 15, 2025, 3:28pm UTC](https://devforum.zoom.us/t/zoom-api-add-assistants-endpoint-stopped-working/137382 "2025-09-15T15:28:38Z")\
**Posts on this page:** 11\
**Page:** 1

<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 15, 2025, 3:28pm UTC](https://devforum.zoom.us/t/zoom-api-add-assistants-endpoint-stopped-working/137382/1 "2025-09-15T15:28:38Z")

</div>

**API Endpoint(s) and/or Zoom API Event(s)**  
”Add assistants” (`/users/{userId}/assistants`)

**Description**  
We run “Add assistants” endpoint requests daily to sync users with scheduling privileges for other users. We started getting errors at 2025-09-14 08:00 AM EDT (`1757851201`) and are still receiving errors now. The response payload when adding multiple assistants (between 2 and 30) looks like the error response payload below.

When a single assistant value is submitted, a successful response is returned but when querying for the user’s assistants the list is still empty.

**Error?**  
`{"code":-1,"message":"Duplicate key null (attempted merging values com.saasbee.webapp.api2.userapi.view.UserAssistant@57f3466e and com.saasbee.webapp.api2.userapi.view.UserAssistant@616228a7)"}`

**How To Reproduce**  
_Steps to reproduce the behavior:_  
_1. Request URL / Headers_: Same as API doc example.  
_2. Authentication method or app type_: OAuth  
_3. Any errors_: See above

---

<div class="post-metadata">

**Author:** ![Josh13](https://avatars.discourse-cdn.com/v4/letter/j/ad7895/32.png) [@Josh13](https://devforum.zoom.us/u/Josh13)\
**Post date:** [September 16, 2025, 8:46am UTC](https://devforum.zoom.us/t/zoom-api-add-assistants-endpoint-stopped-working/137382/2 "2025-09-16T08:46:59Z")

</div>

We have the same issue and opened a ticket, but Zoom support closed it saying to post in the forums.

---

<div class="post-metadata">

**Author:** ![Jack7](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jack7/32/71231_2.png) [@Jack7](https://devforum.zoom.us/u/Jack7)\
**Post date:** [September 16, 2025, 1:19pm UTC](https://devforum.zoom.us/t/zoom-api-add-assistants-endpoint-stopped-working/137382/3 "2025-09-16T13:19:02Z")

</div>

This looks like a Zoom API regression. The `"Duplicate key null"` error suggests the backend is rejecting multiple assistants in a single request. A quick workaround is to add assistants one at a time in a loop — those requests succeed. Also make sure no assistant objects contain `null`/empty values. If it still fails, it’s likely a Zoom-side bug and worth opening a support ticket with your payload.

---

<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, 2:10pm UTC](https://devforum.zoom.us/t/zoom-api-add-assistants-endpoint-stopped-working/137382/4 "2025-09-16T14:10:05Z")

</div>

@Jack7 As I mentioned in my original post, I tried submitting a single assistant and it did not work either. There is no error message, but querying the assistant list always returns an empty list. When I check the Zoom web UI for scheduling privileges, the attempted added user does not show up in the UI either. The delete API request still works though as users added via the UI are wiped out by it.

Like Josh, we originally opened a support ticket, but it was closed saying that the forum was the proper venue which is confusing to me because on the form for opening the ticket there was a message stating:

> Our developer support team is here to assist with **product-related issues** only. If you’re experiencing a problem with our APIs, SDKs, or developer tools, please submit your request using this form.  
> For help with **custom solutions, custom integrations, or feature requests,** please visit our Developer Forum, where our community and experts can provide guidance.

It seems like a product-related issue rather than a custom configuration issue.

---

<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:11pm UTC](https://devforum.zoom.us/t/zoom-api-add-assistants-endpoint-stopped-working/137382/6 "2025-09-16T17:11:33Z")

</div>

Hi @Mutations @Josh13 , please send a recent zm-tracking-id from the response header for the failed request.

Additionally, Josh I’m sorry your ticket was closed. Bug-related issues should be accepted. Can you please tell me what the number is?

---

<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:57pm UTC](https://devforum.zoom.us/t/zoom-api-add-assistants-endpoint-stopped-working/137382/7 "2025-09-16T18:57:07Z")

</div>

Hello @gianni.zoom , thank you for investigating!

Here is a `zm-tracking-id` for request with error: `v=2.0;clid=us06;rid=WEB_065197ba83a9c061aa3b410b4fe01ce7`

Here is a `zm-tracking-id` for request with no error but it doesn’t seem to work (assistant doesn’t show up in the list or subsequent query request): `v=2.0;clid=us06;rid=WEB_a2691279c02aa5f2710768fe73142cd2`

Our original support ticket was also closed which is why I made the forum post. The number was `TS2022029`. After some more emails, it has been reopened as `TS2024698`.

---

<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:41pm UTC](https://devforum.zoom.us/t/zoom-api-add-assistants-endpoint-stopped-working/137382/8 "2025-09-16T20:41:48Z")

</div>

> [@Mutations](#):
>
> Here is a `zm-tracking-id` for request with error: `v=2.0;clid=us06;rid=WEB_065197ba83a9c061aa3b410b4fe01ce7`
> 
> Here is a `zm-tracking-id` for request with no error but it doesn’t seem to work (assistant doesn’t show up in the list or subsequent query request): `v=2.0;clid=us06;rid=WEB_a2691279c02aa5f2710768fe73142cd2`

@Mutations thanks so much for providing this info. I’m leaving some notes internally for the support team member working on this since I can see [from the changelog](https://developers.zoom.us/changelog/users/september-15-2025/) that there were updates to this endpoint that may contribute to a breaking change.

---

<div class="post-metadata">

**Author:** ![Jack7](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jack7/32/71231_2.png) [@Jack7](https://devforum.zoom.us/u/Jack7)\
**Post date:** [September 17, 2025, 12:02am UTC](https://devforum.zoom.us/t/zoom-api-add-assistants-endpoint-stopped-working/137382/9 "2025-09-17T00:02:51Z")

</div>

Thanks for clarifying — if adding even a single assistant returns success but doesn’t persist in the list/UI, then it’s not a payload issue on your side. That points to a backend regression in Zoom’s API. Since the behavior changed suddenly and affects both bulk and single inserts, the only real path forward is for Zoom engineering to fix it. I’d suggest reopening the support ticket and referencing this thread + your test payloads so it gets escalated as a product bug, not a config issue.

---

<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:39pm UTC](https://devforum.zoom.us/t/zoom-api-add-assistants-endpoint-stopped-working/137382/10 "2025-09-17T20:39:16Z")

</div>

@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.

---

<div class="post-metadata">

**Author:** ![Josh13](https://avatars.discourse-cdn.com/v4/letter/j/ad7895/32.png) [@Josh13](https://devforum.zoom.us/u/Josh13)\
**Post date:** [September 17, 2025, 11:40pm UTC](https://devforum.zoom.us/t/zoom-api-add-assistants-endpoint-stopped-working/137382/11 "2025-09-17T23:40:07Z")

</div>

Thank you Gianni for the follow up, much appreciated!

This message is intended only for the person(s) to which it is addressed  
and may contain privileged, confidential and/or insider information.  
If you have received this communication in error, please notify us  
immediately by replying to the message and deleting it from your computer.  
Any disclosure, copying, distribution, or the taking of any action concerning  
the contents of this message and any attachment(s) by anyone other  
than the named recipient(s) is strictly prohibited.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [September 18, 2025, 11:40pm UTC](https://devforum.zoom.us/t/zoom-api-add-assistants-endpoint-stopped-working/137382/12 "2025-09-18T23:40:48Z")

</div>

Closed on September 18, 2025, 11:40pm UTC

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