# API Key generator broken **URL:** \ **Category:** API and Webhooks\ **Created:** [October 9, 2018, 1:11pm UTC](https://devforum.zoom.us/t/api-key-generator-broken/1805 "2018-10-09T13:11:43Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![Sergey\_Temchenko](https://avatars.discourse-cdn.com/v4/letter/s/b19c9b/32.png) [@Sergey\_Temchenko](https://devforum.zoom.us/u/Sergey_Temchenko)\ **Post date:** [October 9, 2018, 1:11pm UTC](https://devforum.zoom.us/t/api-key-generator-broken/1805/1 "2018-10-09T13:11:43Z")
Hello, have another problem. I decided to test your API v2 without your Playground so i generated new access token related on my Api Credentials. When i try to use it i get 124 Invalid access token. I thought the problem with my Api Key/Api Secret that i have already been using with API V1 so i clicked to generate new. Regenerate Secret - works fine, i got new Api Secret. Regenerate Access Token - does nothing. It sends POST AJAX on [https://developer.zoom.us/wp-admin/admin-ajax.php](https://developer.zoom.us/wp-admin/admin-ajax.php), gets 200 empty response and shows me alert with text “undefined”. Anyway i tried to generate new access\_token on [https://jwt.io/#debugger-io](https://jwt.io/#debugger-io), i put new secret and kept old key, took new access\_token, did request and still got 124 invalid access token. What’s wrong with API v2? ---
**Author:** ![michael\_p.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/michael_p.zoom/32/18105_2.png) [@michael\_p.zoom](https://devforum.zoom.us/u/michael_p.zoom)\ **Post date:** [October 9, 2018, 6:05pm UTC](https://devforum.zoom.us/t/api-key-generator-broken/1805/2 "2018-10-09T18:05:17Z")
Hi Sergey,  Will have reported this issue to our Engineers and will get back to you as soon as we find the bug and a workaround. Thanks ---
**Author:** ![michael\_p.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/michael_p.zoom/32/18105_2.png) [@michael\_p.zoom](https://devforum.zoom.us/u/michael_p.zoom)\ **Post date:** [October 12, 2018, 7:23pm UTC](https://devforum.zoom.us/t/api-key-generator-broken/1805/3 "2018-10-12T19:23:57Z")
Hi Sergey,  Is this related to the v2/accounts API?  ---
**Author:** ![Sergey\_Temchenko](https://avatars.discourse-cdn.com/v4/letter/s/b19c9b/32.png) [@Sergey\_Temchenko](https://devforum.zoom.us/u/Sergey_Temchenko)\ **Post date:** [October 15, 2018, 6:36am UTC](https://devforum.zoom.us/t/api-key-generator-broken/1805/4 "2018-10-15T06:36:16Z")
I guess this is related to whole API system. This post is about broken API methods ([https://support.zoom.us/hc/en-us/community/posts/360025854792-Playground-V2-doesn-t-work?page=1#community\_comment\_360002628231](https://support.zoom.us/hc/en-us/community/posts/360025854792-Playground-V2-doesn-t-work?page=1#community_comment_360002628231)) And this post is about broken button on [https://developer.zoom.us/me/#api](https://developer.zoom.us/me/#api) ![](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/1X/f7d26b97aaa7b927a2a438400ecb8aa30f34615f.jpeg) It’s impossible to regenerate access token. May be this occurred because this account is sub-account(with Admin role) and not Master account, but on API V1 this worked fine. ---
**Author:** ![michael\_p.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/michael_p.zoom/32/18105_2.png) [@michael\_p.zoom](https://devforum.zoom.us/u/michael_p.zoom)\ **Post date:** [October 16, 2018, 9:20pm UTC](https://devforum.zoom.us/t/api-key-generator-broken/1805/5 "2018-10-16T21:20:07Z")
Hi Sergey, Can you check the role management page for this role - **Zoom for developers**  and see if (read or write) is checked?   ![](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/1X/a1923d1e63c1564e9e3fe395e7c5e0cb4e4f1858.png) ---
**Author:** ![Together\_Networks](https://avatars.discourse-cdn.com/v4/letter/t/3bc359/32.png) [@Together\_Networks](https://devforum.zoom.us/u/Together_Networks)\ **Post date:** [October 17, 2018, 6:22am UTC](https://devforum.zoom.us/t/api-key-generator-broken/1805/6 "2018-10-17T06:22:56Z")
Yes, it is ![](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/1X/298d6f7d33f3944ac3c5dc65e871612af14d64d9.jpeg) ---
**Author:** ![Sergey\_Temchenko](https://avatars.discourse-cdn.com/v4/letter/s/b19c9b/32.png) [@Sergey\_Temchenko](https://devforum.zoom.us/u/Sergey_Temchenko)\ **Post date:** [October 22, 2018, 8:29am UTC](https://devforum.zoom.us/t/api-key-generator-broken/1805/7 "2018-10-22T08:29:42Z")
Any updates? ---
**Author:** ![michael\_p.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/michael_p.zoom/32/18105_2.png) [@michael\_p.zoom](https://devforum.zoom.us/u/michael_p.zoom)\ **Post date:** [October 23, 2018, 5:02pm UTC](https://devforum.zoom.us/t/api-key-generator-broken/1805/8 "2018-10-23T17:02:20Z")
Hi Sergey,  Can you make sure that your account has Chat history enabled as well? That needs to be enabled since we have IM Chat APIs.  ![](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/1X/6ad19eb566ef209cdeb6f7e8d73956ebdee5ef9e.png) ---
**Author:** ![Together\_Networks](https://avatars.discourse-cdn.com/v4/letter/t/3bc359/32.png) [@Together\_Networks](https://devforum.zoom.us/u/Together_Networks)\ **Post date:** [October 24, 2018, 7:24am UTC](https://devforum.zoom.us/t/api-key-generator-broken/1805/9 "2018-10-24T07:24:37Z")
Chat history is disabled, but question was about API Secret, not about IM Chat History Token. Or these tokens are related to each other?  ---
**Author:** ![michael\_p.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/michael_p.zoom/32/18105_2.png) [@michael\_p.zoom](https://devforum.zoom.us/u/michael_p.zoom)\ **Post date:** [October 24, 2018, 4:19pm UTC](https://devforum.zoom.us/t/api-key-generator-broken/1805/10 "2018-10-24T16:19:04Z")
Hello,  Those tokens are related to each other, as the IM Chat is apart of our APIs. Please enable the IM Chat history and try to generate a access token. Let me know if that works.  Thanks ---
**Author:** ![Sergey\_Temchenko](https://avatars.discourse-cdn.com/v4/letter/s/b19c9b/32.png) [@Sergey\_Temchenko](https://devforum.zoom.us/u/Sergey_Temchenko)\ **Post date:** [October 25, 2018, 7:24am UTC](https://devforum.zoom.us/t/api-key-generator-broken/1805/11 "2018-10-25T07:24:59Z")
Thank you, it works! But it would have been better if you had shown message instead of empty alert) ---
**Author:** ![timothy.corrigan](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/timothy.corrigan/32/201_2.png) [@timothy.corrigan](https://devforum.zoom.us/u/timothy.corrigan)\ **Post date:** [December 5, 2018, 9:58pm UTC](https://devforum.zoom.us/t/api-key-generator-broken/1805/12 "2018-12-05T21:58:46Z")
Is it possible to fix this so it does not require enabling IM Chat History? I am unable to enable IM Chat History for security considerations. ---
**Author:** ![Jonathan\_Champ](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jonathan_champ/32/45_2.png) [@Jonathan\_Champ](https://devforum.zoom.us/u/Jonathan_Champ)\ **Post date:** [January 4, 2019, 6:56pm UTC](https://devforum.zoom.us/t/api-key-generator-broken/1805/13 "2019-01-04T18:56:54Z")
As a workaround, I wonder if it works to enable - get the API key - then disable. ---
**Author:** ![timothy.corrigan](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/timothy.corrigan/32/201_2.png) [@timothy.corrigan](https://devforum.zoom.us/u/timothy.corrigan)\ **Post date:** [January 12, 2019, 12:17am UTC](https://devforum.zoom.us/t/api-key-generator-broken/1805/14 "2019-01-12T00:17:23Z")
Unfortunately, that will not work. Our legal department will not allow us to enable IM chat as it enables it for everyone. I was able to develop a PowerShell script to create the JWT Token, so all is good now.