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
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.
@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.
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.
@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 that there were updates to this endpoint that may contribute to a breaking change.
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.
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.
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.