# Zoom API licensing issue **URL:** \ **Category:** API and Webhooks\ **Created:** [November 18, 2025, 2:27pm UTC](https://devforum.zoom.us/t/zoom-api-licensing-issue/138788 "2025-11-18T14:27:58Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![ITMINDBOX](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/itmindbox/32/72337_2.png) [@ITMINDBOX](https://devforum.zoom.us/u/ITMINDBOX)\ **Post date:** [November 18, 2025, 2:27pm UTC](https://devforum.zoom.us/t/zoom-api-licensing-issue/138788/1 "2025-11-18T14:27:58Z")
* * * ### Format Your New Topic as Follows: **API Endpoint(s) and/or Zoom API Event(s)** > **[Zoom User API](https://developers.zoom.us/docs/api/rest/reference/user/methods/#operation/userUpdate)** > > API Reference for /docs/api/rest/reference/user/methods **Description** We use the Zoom API to assign licenses to users. We recently switched from **Zoom Workplace Business** licenses to **Zoom Workplace Business Plus licenses with the US/CA Unlimited plan**. After that, the `PATCH v2/users/` (or `PATCH v2/users/`) method started returning an error: `[3412] Your request to convert the user type of this basic user to a Licensed user was not approved at this time because your account has reached the permitted maximum number of 1 paying users. Please purchase additional licenses or remove existing paying user(s) from your Users list or the Pending Users list before attempting to convert a basic user to a paying user.` Zoom support suggested that it would be sufficient to change `{“type”: 2}` to `{“type”: 16}` in the request body. After that, the request returns HTTP 204, but the specified user still has a Basic license in the Zoom Workplace console. Support recommended contacting this forum. Does anyone have any suggestions on how to fix this? **How To Reproduce** _Steps to reproduce the behavior:_ _1._ Perform PATCH request to `https://api.zoom.us/v2/users/``` , using `{“type”: 16}` as body and `Content-Type: application/json` as header. _2._ Authentication method - OAuth2 (using billing master account)_._ _3. Errors:_ `Error[3412]` when using `{“type”: 2}`; HTTP 204 OK but no real license changes when using `{“type”: 16}`. ---
**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\ **Post date:** [November 25, 2025, 6:56pm UTC](https://devforum.zoom.us/t/zoom-api-licensing-issue/138788/2 "2025-11-25T18:56:09Z")
Hi @ITMINDBOX Thanks for reaching out to us and welcome to the Zoom Developer Forum. Are you still having this issue on your end? If so, I would need to look further into this and for that, I will ask you to reproduce this issue and share with me the tracking ID found in the response headers so we can take a closer look at this ---
**Author:** ![ITMINDBOX](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/itmindbox/32/72337_2.png) [@ITMINDBOX](https://devforum.zoom.us/u/ITMINDBOX)\ **Post date:** [November 27, 2025, 3:04pm UTC](https://devforum.zoom.us/t/zoom-api-licensing-issue/138788/3 "2025-11-27T15:04:36Z")
Hi @elisa.zoom! Yes, the issue still persists. Here is my tracking ID: `v=2.0;clid=us02;rid=WEB_6569b9d47699d44f4baa5b39a1a3091e` ---
**Author:** ![ITMINDBOX](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/itmindbox/32/72337_2.png) [@ITMINDBOX](https://devforum.zoom.us/u/ITMINDBOX)\ **Post date:** [December 3, 2025, 9:59am UTC](https://devforum.zoom.us/t/zoom-api-licensing-issue/138788/4 "2025-12-03T09:59:00Z")
Dear @elisa.zoom , Hope you are well. Could you please tell us if there are any updates on our issue? ---
**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\ **Post date:** [December 3, 2025, 3:41pm UTC](https://devforum.zoom.us/t/zoom-api-licensing-issue/138788/5 "2025-12-03T15:41:06Z")
> [@ITMINDBOX](#): > > v=2.0;clid=us02;rid=WEB\_6569b9d47699d44f4baa5b39a1a3091e Hi @ITMINDBOX Thanks for your patience and sorry for the late reply here! I created an internal ticket for our Engineering team to look into it ( ZSEE-188102 internal ticket number for reference) ---
**Author:** ![ITMINDBOX](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/itmindbox/32/72337_2.png) [@ITMINDBOX](https://devforum.zoom.us/u/ITMINDBOX)\ **Post date:** [January 12, 2026, 4:44pm UTC](https://devforum.zoom.us/t/zoom-api-licensing-issue/138788/6 "2026-01-12T16:44:27Z")
Hi @elisa.zoom ! Could you please let me know if there are any updates here? ---
**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:** [January 13, 2026, 3:29pm UTC](https://devforum.zoom.us/t/zoom-api-licensing-issue/138788/7 "2026-01-13T15:29:39Z")
> [@elisa.zoom](#): > > ZSEE-188102 @ITMINDBOX , here’s what our service engineering team shared: I’ve checked the backend data and can confirm that the user hasn’t been updated. The developer is using an incorrect key ( **type:16** ) in the API request, which is not valid for the license plan type. Please request them to follow the API documentation and use the correct **key:value** pair to update the user. [Users APIs](https://developers.zoom.us/docs/api/users/#tag/users/patch/users/%7BuserId%7D) Here are the possible key-value pairs: ![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/a/c/acc05be5d31b5bb8717033b974abf044c86822f9.png) ![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/0/60154351bca545ff1d4e384e291663d12ea17345.png) Can you try this and get back to us? ---
**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:** [January 16, 2026, 1:57pm UTC](https://devforum.zoom.us/t/zoom-api-licensing-issue/138788/8 "2026-01-16T13:57:14Z")
Hi @ITMINDBOX , just following up! Thanks!