# Invite URL password hash

**URL:** <https://devforum.zoom.us/t/invite-url-password-hash/3363>\
**Category:** API and Webhooks\
**Created:** [February 22, 2019, 3:32pm UTC](https://devforum.zoom.us/t/invite-url-password-hash/3363 "2019-02-22T15:32:16Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**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:** [April 3, 2020, 3:44am UTC](https://devforum.zoom.us/t/invite-url-password-hash/3363/11 "2020-04-03T03:44:40Z")

</div>

Hey @bizstim.apps, and everyone,

Here is a the request/response from a meeting I just created with a password:

POST [https://api.zoom.us/v2/users/me/meetings](https://api.zoom.us/v2/users/me/meetings)

BODY:

```json
{
	"topic":"Test Password",
	"type":2,
	"start_time": "2020:04:05T00:00:00Z",
	"duration": 30,
	"password": "1234@"
}

```

Response:

```json
{
    "uuid": "",
    "id":,
    "host_id": "",
    "topic": "Test Password",
    "type": 2,
    "status": "waiting",
    "start_time": "2020-04-03T03:39:39Z",
    "duration": 30,
    "timezone": "America/Denver",
    "created_at": "2020-04-03T03:39:39Z",
    "start_url": "",
    "join_url": "https://tommygaessler.zoom.us/j/meetingID?pwd=UjJQTENnamVFMEpQN2tVUHRHZmY4Zz09",
    "password": "1234@",
    "h323_password": "232607",
    "pstn_password": "232607",
    "encrypted_password": "UjJQTENnamVFMEpQN2tVUHRHZmY4Zz09",
    "pmi": "",
    "settings": {
...

```

As you can see there are variations of the password, and the join\_url has the encrypted password already so clicking on the join\_url will automatically pass in the password.

If typing in the password, you will use in the numeric password.

Does that clear things up?

The hash is generated via our backend and we cannot share the algorithm that does this to generate the hash with the plain text meeting password.

Thanks,  
Tommy

---

_[View the full topic](https://devforum.zoom.us/t/invite-url-password-hash/3363)._