# Send registrants **URL:** \ **Category:** API and Webhooks\ **Created:** [May 5, 2020, 8:51pm UTC](https://devforum.zoom.us/t/send-registrants/16301 "2020-05-05T20:51:31Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![alorentz](https://avatars.discourse-cdn.com/v4/letter/a/3d9bf3/32.png) [@alorentz](https://devforum.zoom.us/u/alorentz)\ **Post date:** [May 5, 2020, 8:51pm UTC](https://devforum.zoom.us/t/send-registrants/16301/1 "2020-05-05T20:51:31Z")
Due to the Web SDK not having computer audio support for Firefox and Safari, I’m considering the registration API: [https://marketplace.zoom.us/docs/api-reference/zoom-api/meetings/meetingregistrantcreate](https://marketplace.zoom.us/docs/api-reference/zoom-api/meetings/meetingregistrantcreate), to use the join\_url to allow each person access to the event. However, these requests appear to require oauth\_access\_token, which required Client ID and Client Secret, which I created in the MarketPlace. However, when using the **Send a Test Request** function, I needed to enter the key and secret into the popup to generate the oauth\_access\_token, which asked me to approve access to the app. That approval seems related to each user. Is that correct? I’d like to send a list of all registrants (in our database) for a meeting or webinar via API, but how do I get an access token that simply allows the code to send the registrants, an access code non-specific to each registrant nor requiring approval? I’m sure I’m missing something obvious. ---
**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:** [May 8, 2020, 6:22pm UTC](https://devforum.zoom.us/t/send-registrants/16301/2 "2020-05-08T18:22:20Z")
Hi @alorentz, you can use [JSON Web Tokens](https://marketplace.zoom.us/docs/guides/auth/jwt) with your account-level API Key & Secret to add registrants to meetings **on your account**. If you want to add registrants for meetings outside of your account, you will need to use [OAuth](https://marketplace.zoom.us/docs/guides/auth/oauth). ---
**Author:** ![alorentz](https://avatars.discourse-cdn.com/v4/letter/a/3d9bf3/32.png) [@alorentz](https://devforum.zoom.us/u/alorentz)\ **Post date:** [May 8, 2020, 6:46pm UTC](https://devforum.zoom.us/t/send-registrants/16301/3 "2020-05-08T18:46:22Z")
Are there docs on adding registrants using JSON Web Tokens? ---
**Author:** ![alorentz](https://avatars.discourse-cdn.com/v4/letter/a/3d9bf3/32.png) [@alorentz](https://devforum.zoom.us/u/alorentz)\ **Post date:** [May 13, 2020, 6:16pm UTC](https://devforum.zoom.us/t/send-registrants/16301/4 "2020-05-13T18:16:04Z")
Are there docs on adding registrants using JSON Web Tokens? ---
**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:** [May 13, 2020, 7:54pm UTC](https://devforum.zoom.us/t/send-registrants/16301/5 "2020-05-13T19:54:21Z")
Hi @alorentz, any API request (for data on your account) can be authenticated using JSON Web Tokens. [API Reference: Add a Meeting Registrant.](https://marketplace.zoom.us/docs/api-reference/zoom-api/meetings/meetingregistrantcreate). Generate these tokens on a backend service, then pass the token as Bearer Token in the Authorization header of the request. ---
**Author:** ![alorentz](https://avatars.discourse-cdn.com/v4/letter/a/3d9bf3/32.png) [@alorentz](https://devforum.zoom.us/u/alorentz)\ **Post date:** [May 13, 2020, 8:56pm UTC](https://devforum.zoom.us/t/send-registrants/16301/6 "2020-05-13T20:56:02Z")
@michael.zoom - I posted the /memberregistercreate reference initially, which is what I’m questions. For JWT Web Tokens, is Bearer Token different than “signature”. For example, I’ve used signature when establishing a web client meeting. Such as: (see signature reference) ZoomMtg.setZoomJSLib(‘[https://dmogdx0jrul3u.cloudfront.net/1.7.6/lib](https://dmogdx0jrul3u.cloudfront.net/1.7.6/lib)’, ‘/av’); ``` ZoomMtg.preLoadWasm(); ZoomMtg.prepareJssdk(); ZoomMtg.init({ leaveUrl: leaveUrl, isSupportAV: true, success: function() { ZoomMtg.join({ signature: signature, apiKey: apiKey, meetingNumber: meetingNum, userName:user, // Email required for Webinars userEmail: email, // password optional; set by Host passWord: password, error(res) { console.log(res) } }) } }) ``` ---
**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:** [May 13, 2020, 8:58pm UTC](https://devforum.zoom.us/t/send-registrants/16301/7 "2020-05-13T20:58:43Z")
@alorentz, yes this signature you’re using here is to secure the meeting join function within the Web SDK. JSON Web Tokens also have a signature which you need to sign using your API Secret. ---
**Author:** ![alorentz](https://avatars.discourse-cdn.com/v4/letter/a/3d9bf3/32.png) [@alorentz](https://devforum.zoom.us/u/alorentz)\ **Post date:** [May 13, 2020, 9:15pm UTC](https://devforum.zoom.us/t/send-registrants/16301/8 "2020-05-13T21:15:42Z")
Can you clarify base don my previous question? For JWT Web Tokens, is Bearer Token different than “signature”? Or, would the Bearer Token be the signature, generated the same way as done for the script above? ---
**Author:** ![alorentz](https://avatars.discourse-cdn.com/v4/letter/a/3d9bf3/32.png) [@alorentz](https://devforum.zoom.us/u/alorentz)\ **Post date:** [May 13, 2020, 9:19pm UTC](https://devforum.zoom.us/t/send-registrants/16301/9 "2020-05-13T21:19:17Z")
@michael.zoom For example, see PHP example here for function generate\_signature : > **[Generate Signature - Essential Guides - Web - Native SDKs - Zoom Software...](https://marketplace.zoom.us/docs/sdk/native-sdks/web/essential/signature)** > > Generate Signature > > Each request to Start or Join a Meeting / Webinar must be verified by an encrypted signature authorizing the user to enter. > > The sig... Woudl I use the same function to generate a bearer token? Or is a bearer token different than a signature? ---
**Author:** ![alorentz](https://avatars.discourse-cdn.com/v4/letter/a/3d9bf3/32.png) [@alorentz](https://devforum.zoom.us/u/alorentz)\ **Post date:** [May 14, 2020, 8:32pm UTC](https://devforum.zoom.us/t/send-registrants/16301/10 "2020-05-14T20:32:28Z")
@michael.zoom @michael_p.zoom following up in my last comment…? ---
**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\ **Post date:** [May 19, 2020, 4:45pm UTC](https://devforum.zoom.us/t/send-registrants/16301/11 "2020-05-19T16:45:45Z")
Hey @alorentz, A [JWT App](https://marketplace.zoom.us/docs/guides/build/jwt-app), does generate both a JWT Token and Web SDK Signature. However, they are different. The [JWT Token](https://marketplace.zoom.us/docs/guides/auth/jwt) is used to call the [Zoom APIs](https://marketplace.zoom.us/docs/api-reference/zoom-api): `"Authorization":"Bearer JWT_TOKEN_HERE"` The [Web SDK Signature](https://marketplace.zoom.us/docs/sdk/native-sdks/web/essential/signature) is used to join and start meetings / webinars with the [Web SDK](https://marketplace.zoom.us/docs/sdk/native-sdks/web). Does that answer your question? Thanks, Tommy ---
**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, 9:25pm UTC](https://devforum.zoom.us/t/send-registrants/16301/12 "2020-08-21T21:25:00Z")
Closed on August 21, 2020, 9:25pm UTC