# Zoom App requests passcode even with hashed password in link

**URL:** <https://devforum.zoom.us/t/zoom-app-requests-passcode-even-with-hashed-password-in-link/36387>\
**Category:** API and Webhooks\
**Created:** [November 18, 2020, 8:15pm UTC](https://devforum.zoom.us/t/zoom-app-requests-passcode-even-with-hashed-password-in-link/36387 "2020-11-18T20:15:16Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![pgtaboada](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/pgtaboada/32/3562_2.png) [@pgtaboada](https://devforum.zoom.us/u/pgtaboada)\
**Post date:** [November 18, 2020, 8:15pm UTC](https://devforum.zoom.us/t/zoom-app-requests-passcode-even-with-hashed-password-in-link/36387/1 "2020-11-18T20:15:16Z")

</div>

**Description**

Our marketplace App creates Zoom-Meetings and stores the join url. We send the URL to attendees, and lately we started receiving more and more complaints that the attendees need to enter the passcode. The problem is: we only send the join url with the hashed passcode. Attendees therefore are not able to join the meeting.

**Error**  
Passcode is requested although the join url contains the hashcode

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

Published OAuth App

**How To Reproduce (If applicable)**

We cannot reproduce. The join urls are correct, but the passcode is (not always) requested.

---

<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:** [November 19, 2020, 5:44pm UTC](https://devforum.zoom.us/t/zoom-app-requests-passcode-even-with-hashed-password-in-link/36387/2 "2020-11-19T17:44:34Z")

</div>

Hey @pgtaboada,

Can you share an example of a Meeting ID or screenshot where an attendee was required to enter a passcode? I’m happy to look into it for you if there’s an example I can take a look at.

Thanks!  
Will

---

<div class="post-metadata">

**Author:** ![pgtaboada](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/pgtaboada/32/3562_2.png) [@pgtaboada](https://devforum.zoom.us/u/pgtaboada)\
**Post date:** [November 19, 2020, 6:01pm UTC](https://devforum.zoom.us/t/zoom-app-requests-passcode-even-with-hashed-password-in-link/36387/3 "2020-11-19T18:01:18Z")

</div>

Unfortunately not - it does not happen every time. I witnessed it just once, but we have several complaints in our ticket system. We had the suspicion, that it happened when the attendee tried to join before the host, but that is not the case (anymore?).

Is there any (new?) setting that could trigger such behaviour?

---

<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:** [November 20, 2020, 9:46pm UTC](https://devforum.zoom.us/t/zoom-app-requests-passcode-even-with-hashed-password-in-link/36387/4 "2020-11-20T21:46:45Z")

</div>

Hey @pgtaboada,

Can you ensure that your requests and account/user settings are such that the password is provided in the API Create Meeting response? You can find a breakdown of this here:

> **[Announcements - Stay Up To Date - Documentation](https://marketplace.zoom.us/docs/guides/stay-up-to-date/announcements#passcode-and-wr-changes)**
>
> Announcements
> 
> Below are upcoming and recent backwards compatible changes made to the Zoom Developer Platform. For other recent changes to the Zoom API,...

Thanks,  
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:** [December 21, 2020, 7:46am UTC](https://devforum.zoom.us/t/zoom-app-requests-passcode-even-with-hashed-password-in-link/36387/5 "2020-12-21T07:46:49Z")

</div>

Closed on December 21, 2020, 7:46am UTC

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