# URGENT: all API calls returning Invalid token.

**URL:** <https://devforum.zoom.us/t/urgent-all-api-calls-returning-invalid-token/1362>\
**Category:** API and Webhooks\
**Created:** [June 18, 2018, 12:08pm UTC](https://devforum.zoom.us/t/urgent-all-api-calls-returning-invalid-token/1362 "2018-06-18T12:08:03Z")\
**Posts on this page:** 3\
**Page:** 2

<div class="post-metadata">

**Author:** ![David\_Pereira](https://avatars.discourse-cdn.com/v4/letter/d/f14d63/32.png) [@David\_Pereira](https://devforum.zoom.us/u/David_Pereira)\
**Post date:** [June 19, 2018, 8:17am UTC](https://devforum.zoom.us/t/urgent-all-api-calls-returning-invalid-token/1362/21 "2018-06-19T08:17:08Z")

</div>

Hi Tim,

Just to let you know:

- _Can you try using the [JWT.io](http://JWT.io) library? We have had much greater success with this with all of our clients. It is very easy to implement. Can you try this and let me know if this resolves the problem?&nbsp;_
- As we replied yesterday night, we are using the official .NET library for JWT. it has almost 2 millions of downloads.

&nbsp;

- _Are you on v5.1.5? Can you try the latest version?&nbsp;_
- I just updated it to v5.2.2 and it’s not working. Code 124, Invalid access token.&nbsp;

&nbsp;

- _Are you generating short-lived tokens or are you using a token that has a chance to be expired?_
- They expire in 60 minutes.&nbsp;

We are also in talks with some of your colleagues over email channel. We just sent to Dan Fan a Token which expires in 10 hours (maybe 9 from now). Do you want me to resend my email to [developersupport@zoom.us](mailto:developersupport@zoom.us)?

Anyway, we were told yesterday night that you would release a fix for this. Did you release that fix finally?&nbsp;

If you need more details do not hesitate to contact us again,&nbsp;

Regards,

&nbsp;

David Pereira

---

<div class="post-metadata">

**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:** [June 19, 2018, 12:40pm UTC](https://devforum.zoom.us/t/urgent-all-api-calls-returning-invalid-token/1362/22 "2018-06-19T12:40:32Z")

</div>

Hi Everyone,&nbsp;

Our Engineering team has made an update to resolve the “invalid access token” error. For transparency about the issue, we updated our JWT library to only accept HS256 alg as stated in our [docs](https://zoom.github.io/api/#authentication) and previously we would accept HS512 alg as well. We have made an emergency fix to allow both HS512 and HS256 alg to call our APIs.&nbsp;

Please let us know if that works or you are still having issues.&nbsp;

Thanks

&nbsp;

---

<div class="post-metadata">

**Author:** ![DeveloperBot](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/developerbot/32/12632_2.png) [@DeveloperBot](https://devforum.zoom.us/u/DeveloperBot)\
**Post date:** [August 21, 2020, 5:49pm UTC](https://devforum.zoom.us/t/urgent-all-api-calls-returning-invalid-token/1362/23 "2020-08-21T17:49:30Z")

</div>

Closed on August 21, 2020, 5:49pm UTC



[Previous page](https://devforum.zoom.us/t/urgent-all-api-calls-returning-invalid-token/1362.md?page=1)
