# Generate Access Token to create meeting

**URL:** <https://devforum.zoom.us/t/generate-access-token-to-create-meeting/20545>\
**Category:** API and Webhooks\
**Created:** [June 7, 2020, 7:07am UTC](https://devforum.zoom.us/t/generate-access-token-to-create-meeting/20545 "2020-06-07T07:07:08Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![just2hafsal](https://avatars.discourse-cdn.com/v4/letter/j/46a35a/32.png) [@just2hafsal](https://devforum.zoom.us/u/just2hafsal)\
**Post date:** [June 7, 2020, 7:07am UTC](https://devforum.zoom.us/t/generate-access-token-to-create-meeting/20545/1 "2020-06-07T07:07:08Z")

</div>

**Description**  
After little Research and coding now i can create and join A meeting with WEB CDN and API.

To create meeting an access token is required, and currently iam generating access token using Client ID and Client Secret.

but it seems to be expire after a while and not possible to create through API, so is there any solution to generate Access Token with JWT?  
or  
can i create a meeting on my account through Simple API (with JWT)?

---

<div class="post-metadata">

**Author:** ![michael.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/michael.zoom/32/37213_2.png) [@michael.zoom](https://devforum.zoom.us/u/michael.zoom)\
**Post date:** [June 10, 2020, 4:52pm UTC](https://devforum.zoom.us/t/generate-access-token-to-create-meeting/20545/2 "2020-06-10T16:52:06Z")

</div>

Hi @just2hafsal when you receive an access token, you also receive a `refresh_token` which can be stored and then used to request a new (refreshed) access\_token.

JWT can also be used to authenticate any request for users on your account. Follow our documentation here to generate these tokens on each request:

> **[JSON Web Tokens (JWT) - Authorization - Documentation](https://marketplace.zoom.us/docs/guides/auth/jwt)**
>
> JWT With Zoom
> 
> The Zoom API uses JSON Web Tokens (JWT) to authenticate account-level access. These tokens offer a method to establish secure server-to-s...

---

<div class="post-metadata">

**Author:** ![OregonDean](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/oregondean/32/10443_2.png) [@OregonDean](https://devforum.zoom.us/u/OregonDean)\
**Post date:** [June 12, 2020, 6:07pm UTC](https://devforum.zoom.us/t/generate-access-token-to-create-meeting/20545/3 "2020-06-12T18:07:20Z")

</div>

Hi @michael.zoom - can you elaborate on the refresh\_token?

I’m also curious as to why Zoom does not offer a standalone microservice or API to create and update JWT’s.

Thanks!

---

<div class="post-metadata">

**Author:** ![michael.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/michael.zoom/32/37213_2.png) [@michael.zoom](https://devforum.zoom.us/u/michael.zoom)\
**Post date:** [June 17, 2020, 6:56pm UTC](https://devforum.zoom.us/t/generate-access-token-to-create-meeting/20545/4 "2020-06-17T18:56:51Z")

</div>

Hi @OregonDean, a refresh token is passed each time you request an access token in the [OAuth](https://marketplace.zoom.us/docs/guides/auth/oauth) process. Access tokens are valid for one hour. To request a new token, you use the refresh\_token given in the response. Refresh tokens are valid for one use, so when you get the new access token, you’ll need to also cache/store the updated refresh token.

We don’t provide a standalone microservice to generate JWT because we want to use the single token transfer to check if the API Key included in the payload of the request matches the API Secret the token has been signed with. We want you to handle that signing process, not a microservice which would have to transfer credentials.

---

<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, 10:06pm UTC](https://devforum.zoom.us/t/generate-access-token-to-create-meeting/20545/5 "2020-08-21T22:06:09Z")

</div>


