How To Reproduce (If applicable)
Steps to reproduce the behavior:
Request URL / Headers (without credentials) / Body
See error
Screenshots (If applicable)
If applicable, add screenshots to help explain your problem.
Additional context
It appears many people raised this concern in last year, I am not the first one. No where I found the response, instead tickets are closed.
Thank you for reaching out about this, and happy to help.
To clarify, are you specifying the disassociate or delete parameter in your request URL? Can you share the full request URL you’re using? Additionally, can you confirm that the user you’re deleting has active meetings/data to transfer?
Can you please confirm that you’re passing the necessary parameters as part of the request URL and not as part of a request body? Note that these should be query parameters, this request has no body:
Thanks Will, it worked with query/request parameters, tested with postman.
After the deletion when I try to re-create the same user from Admin login so that I can test from my Java code ran into following error. Doesn’t give more details simply says data error and asked me to contact Zoom. Please see the screenshot below, can you please help me what is going wrong?
Can you please share these details/screenshot with our Technical Support team here? They will be be best suited to troubleshoot this error and help resolve.
I called the customer support, they helped me figure-out.
Here is what happened:
Upon the deletion account with that email became basic, when I use the same email to send invitation is not working from company account (add user). Instead I signed up as a basic user with the same email then I received activation link, and I activate the zoom basic, then as an admin from company account I invited the user, then It worked.
Also, I noticed, when I used transfer_webinar = true, request is failing, I realized webinar is different subscription we don’t have. When I removed this parameter, deletion was successful.
I’m glad to hear that they resolved your issue! Thank you for posting the solution here. Please don’t hesitate to reach out if you encounter any further issues or questions.