# Documentation missing when a role is successfully created

**URL:** <https://devforum.zoom.us/t/documentation-missing-when-a-role-is-successfully-created/141665>\
**Category:** API and Webhooks\
**Created:** [February 4, 2026, 12:18am UTC](https://devforum.zoom.us/t/documentation-missing-when-a-role-is-successfully-created/141665 "2026-02-04T00:18:03Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![desautelsj](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/desautelsj/32/23584_2.png) [@desautelsj](https://devforum.zoom.us/u/desautelsj)\
**Post date:** [February 4, 2026, 12:18am UTC](https://devforum.zoom.us/t/documentation-missing-when-a-role-is-successfully-created/141665/1 "2026-02-04T00:18:03Z")

</div>

Sending a POST request to [https://api.zoom.us/v2/roles](https://api.zoom.us/v2/roles), you get a HTTP 201 response with the JSON representation of the newly created role in the payload. However, this is not [documented](https://developers.zoom.us/docs/api/accounts/#tag/roles/post/roles).

Can the documentation please be updated to document the expected JSON in the response?

---

<div class="post-metadata">

**Author:** ![expertswho](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/expertswho/32/60945_2.png) [@expertswho](https://devforum.zoom.us/u/expertswho)\
**Post date:** [February 4, 2026, 10:50am UTC](https://devforum.zoom.us/t/documentation-missing-when-a-role-is-successfully-created/141665/2 "2026-02-04T10:50:44Z")

</div>

@desautelsj  
As an MVP you can submit a request to documentation.  
Message Elisa via our team chat.

John

---

<div class="post-metadata">

**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:** [February 4, 2026, 2:23pm UTC](https://devforum.zoom.us/t/documentation-missing-when-a-role-is-successfully-created/141665/3 "2026-02-04T14:23:19Z")

</div>

Thanks for reporting this @desautelsj  
I created an internal ticket for our Engineering team to add this to the API spec  
(ZSEE-193747 internal ticket number for reference)
