# Invalid access token with server-side token JWT

**URL:** <https://devforum.zoom.us/t/invalid-access-token-with-server-side-token-jwt/43515>\
**Category:** API and Webhooks\
**Created:** [February 16, 2021, 8:42pm UTC](https://devforum.zoom.us/t/invalid-access-token-with-server-side-token-jwt/43515 "2021-02-16T20:42:12Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![micu](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/micu/32/23182_2.png) [@micu](https://devforum.zoom.us/u/micu)\
**Post date:** [February 16, 2021, 8:42pm UTC](https://devforum.zoom.us/t/invalid-access-token-with-server-side-token-jwt/43515/1 "2021-02-16T20:42:12Z")

</div>

**Description**  
Trying to generate a JWS token in a C# application, when testing the generated token with Postman I receive an “Invalid access token”.

**Error**  
{

```
"code": 124,

"message": "Invalid access token"

```

}

**Which App Type (OAuth / Chatbot / JWT / Webhook)?**  
JWT

**Which Endpoint/s?**  
[https://api.zoom.us/v2/phone/users](https://api.zoom.us/v2/phone/users)

**Additional context**  
When testing the same endpoint with the JWT generated within the Zoom marketplace, authorization worked fine, only server-side generated tokens fail. I decoded the generated token with [https://jwt.io/](https://jwt.io/) and everything looks fine.

---

<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:** [February 16, 2021, 8:43pm UTC](https://devforum.zoom.us/t/invalid-access-token-with-server-side-token-jwt/43515/2 "2021-02-16T20:43:21Z")

</div>

Hey @micu

Thanks for posting on the Zoom Devforum! I am still learning, but I will try my best to help answer your question. 🙂

Checkout these related threads that may have the answer you are looking for:

> [@Invalid Access token for calls to /accounts endpoint](https://devforum.zoom.us/t/-/23675):
>
> Description We receive an “Invalid Access token” error when attempting to access the /accounts endpoint. The token appears to work for other endpoints. Error { code: 124, message: ‘Invalid access token.’ } Which App Type (OAuth / Chatbot / JWT / Webhook)? JWT Which Endpoint/s? /accounts Additional context We also receive the token error when testing access on the endpoint page [https://marketplace.zoom.us/docs/api-reference/zoom-api/accounts/accounts](https://marketplace.zoom.us/docs/api-reference/zoom-api/accounts/accounts) The token appears to work for s…

> [@Access Token not working for some APIs](https://devforum.zoom.us/t/-/23519):
>
> Description I have made an OAuth app and generated access and refresh tokens for the same. The tokens were working fine for the APIs I hit, except few where i get error code 124. Error When using the api [https://marketplace.zoom.us/docs/api-reference/zoom-api/accounts/getaccountlocksettings](https://marketplace.zoom.us/docs/api-reference/zoom-api/accounts/getaccountlocksettings) I get error code 124 and message the access token invalid on postman. Other APIs are working fine. Which App Type (OAuth / Chatbot / JWT / Webhook)? OAuth

If these threads did not help, please let us know by replying back here and someone from the Developer Relations team will get back to you shortly.

Thanks,  
DeveloperBot

---

<div class="post-metadata">

**Author:** ![micu](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/micu/32/23182_2.png) [@micu](https://devforum.zoom.us/u/micu)\
**Post date:** [February 16, 2021, 8:44pm UTC](https://devforum.zoom.us/t/invalid-access-token-with-server-side-token-jwt/43515/3 "2021-02-16T20:44:16Z")

</div>

Looked into those threads. Not related, I believe.

---

<div class="post-metadata">

**Author:** ![will.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/will.zoom/32/14417_2.png) [@will.zoom](https://devforum.zoom.us/u/will.zoom)\
**Post date:** [February 17, 2021, 7:31pm UTC](https://devforum.zoom.us/t/invalid-access-token-with-server-side-token-jwt/43515/4 "2021-02-17T19:31:12Z")

</div>

Hey @micu,

Thanks for reaching out about this, and happy to help.

Are you using the C# library from [jwt.io](http://jwt.io), or a different library? Can you let me know if this thread helps:  
[C# JWT token invalid - #6 by tommy](https://devforum.zoom.us/t/c-jwt-token-invalid/5968/6)

If the JWT token generated via the Zoom marketplace is working for you, this is most likely an issue with the code you’re using to generate the token programmatically.

Let me know if either of the resources linked in the attached thread help, though!

Best,  
Will

---

<div class="post-metadata">

**Author:** ![micu](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/micu/32/23182_2.png) [@micu](https://devforum.zoom.us/u/micu)\
**Post date:** [February 23, 2021, 11:50am UTC](https://devforum.zoom.us/t/invalid-access-token-with-server-side-token-jwt/43515/5 "2021-02-23T11:50:48Z")

</div>

Hi @will.zoom,

Thanks for helping. Yes, I was using a C# library from [jwt.io](http://jwt.io). I ended up using a different library listed there and that solved my problem.

---

<div class="post-metadata">

**Author:** ![will.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/will.zoom/32/14417_2.png) [@will.zoom](https://devforum.zoom.us/u/will.zoom)\
**Post date:** [February 23, 2021, 4:00pm UTC](https://devforum.zoom.us/t/invalid-access-token-with-server-side-token-jwt/43515/6 "2021-02-23T16:00:45Z")

</div>

Hey @micu,

Glad to hear that switching libraries did the trick!

Best,  
Will

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [March 26, 2021, 2:01am UTC](https://devforum.zoom.us/t/invalid-access-token-with-server-side-token-jwt/43515/7 "2021-03-26T02:01:07Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
