# Hosed by your host\_key removal

**URL:** <https://devforum.zoom.us/t/hosed-by-your-host-key-removal/75121>\
**Category:** Users and Groups\
**Created:** [August 30, 2022, 11:35am UTC](https://devforum.zoom.us/t/hosed-by-your-host-key-removal/75121 "2022-08-30T11:35:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dbailey](https://avatars.discourse-cdn.com/v4/letter/d/50afbb/32.png) [@dbailey](https://devforum.zoom.us/u/dbailey)\
**Post date:** [August 30, 2022, 11:35am UTC](https://devforum.zoom.us/t/hosed-by-your-host-key-removal/75121/1 "2022-08-30T11:35:03Z")

</div>

We obtained the host\_key from the user API and sent it out in communications to our faculty. Now it’s not going out because of your “breaking change”.

Do you have an example I could review to resolve this?

---

<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:** [August 31, 2022, 1:31am UTC](https://devforum.zoom.us/t/hosed-by-your-host-key-removal/75121/2 "2022-08-31T01:31:05Z")

</div>

Hi @dbailey  
Thanks for reaching out to the Zoom Developer Forum, I am happy to help here!  
Feel free to check out this post about Alternatives to using “host\_key”

> [@Alternatives to using the \`host\_key\`](https://devforum.zoom.us/t/alternatives-to-using-the-host-key/74422):
>
> With the latest update to the Zoom API, developers will no longer be able to access a user’s host\_key value. We understand that this is a breaking change and may alter the workflow of some applications. Below are two possible modifications you can make instead of using the host\_key value. If your use case isn’t mentioned, contact customer support and we will assist you in finding a path forward. Use-Case 1: Enterprise customers that want to integrate Zoom user profiles with their IDP/ActiveDir…

Hope this helps,  
Elisa