# How to encode email for "/users/{userId}/meetings" endpoint

**URL:** <https://devforum.zoom.us/t/how-to-encode-email-for-users-userid-meetings-endpoint/41627>\
**Category:** API and Webhooks\
**Created:** [January 26, 2021, 6:07pm UTC](https://devforum.zoom.us/t/how-to-encode-email-for-users-userid-meetings-endpoint/41627 "2021-01-26T18:07:14Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![sboeser](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/sboeser/32/19069_2.png) [@sboeser](https://devforum.zoom.us/u/sboeser)\
**Post date:** [January 26, 2021, 6:07pm UTC](https://devforum.zoom.us/t/how-to-encode-email-for-users-userid-meetings-endpoint/41627/1 "2021-01-26T18:07:15Z")

</div>

**Description**  
I have users with a plus sign “+” in their email address. The “/users/{userId}/meetings” endpoint specifies that {userId} can be UUID or email address. (How) can I encode the email address to still form a valid request?

Happy to take “No.” for an answer…

**Error**

- Not encoding the email address yields 404 Client error
- Quoting the plus and @-sign yields 404 Client error
- Quoting just the plus sign yields 404 Client error

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

**Which Endpoint/s?**  
/users/{userId}/meetings

---

<div class="post-metadata">

**Author:** ![MaxM](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/maxm/32/42303_2.png) [@MaxM](https://devforum.zoom.us/u/MaxM)\
**Post date:** [January 26, 2021, 11:21pm UTC](https://devforum.zoom.us/t/how-to-encode-email-for-users-userid-meetings-endpoint/41627/2 "2021-01-26T23:21:53Z")

</div>

Hey @sboeser,

Thank you for reaching out to the Zoom Developer Forum. In order to allow an email with a plus sign to be used in a URL, you’ll want to URL encode the email address. This can be done in code, let me know what you’re using and I can be more specific. Otherwise, you can test out encoding the emails using the following link:

[https://www.w3schools.com/tags/ref\_urlencode.ASP](https://www.w3schools.com/tags/ref_urlencode.ASP)

Let me know if that helps.

Thanks,  
Max

---

<div class="post-metadata">

**Author:** ![sboeser](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/sboeser/32/19069_2.png) [@sboeser](https://devforum.zoom.us/u/sboeser)\
**Post date:** [January 27, 2021, 10:55am UTC](https://devforum.zoom.us/t/how-to-encode-email-for-users-userid-meetings-endpoint/41627/3 "2021-01-27T10:55:06Z")

</div>

Dear Max,

unfortunately, your proposed solution does not work. I had tried this before (see above). Here are a few more details about my test:

- I am using python with `requests` library, which works fine on email address w/o a plus sign.
- The email I have is `REDACTED`. I have used `urllib.parse.quote` to encode this, which yields `REDACTED`.
- The link you propose for testing yiels `REDACTED` which looks identical to me. Pasting this into my request also yields a 404.
- Using the UUID of the user instead, I can access the endpoint w/o any issues (i.e. this is not an authentication issue).

Thanks,  
Sebastian

---

<div class="post-metadata">

**Author:** ![MaxM](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/maxm/32/42303_2.png) [@MaxM](https://devforum.zoom.us/u/MaxM)\
**Post date:** [January 28, 2021, 12:44am UTC](https://devforum.zoom.us/t/how-to-encode-email-for-users-userid-meetings-endpoint/41627/4 "2021-01-28T00:44:28Z")

</div>

Hey @sboeser,

Thank you for providing additional information. I tested this on my end and saw that I was able to make this request even without encoding the email. When looking at your account, I saw that a user with the email “[REDACTED]” does not exist. Instead, it looks like the email to use ends with @gmail.com.

Please check the [User Management Page](https://zoom.us/account/user#/) in your Zoom portal to confirm this.

Thanks,  
Max

---

<div class="post-metadata">

**Author:** ![sboeser](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/sboeser/32/19069_2.png) [@sboeser](https://devforum.zoom.us/u/sboeser)\
**Post date:** [January 28, 2021, 8:11am UTC](https://devforum.zoom.us/t/how-to-encode-email-for-users-userid-meetings-endpoint/41627/5 "2021-01-28T08:11:59Z")

</div>

Sorry - my bad!!! 🤦‍♂️

---

<div class="post-metadata">

**Author:** ![MaxM](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/maxm/32/42303_2.png) [@MaxM](https://devforum.zoom.us/u/MaxM)\
**Post date:** [January 29, 2021, 1:36am UTC](https://devforum.zoom.us/t/how-to-encode-email-for-users-userid-meetings-endpoint/41627/6 "2021-01-29T01:36:47Z")

</div>

Hey @sboeser,

No worries, I’m glad we were able to get that sorted out! It’s my mistake for not checking that earlier. Feel free to reach out if you encounter any other issues or questions.

Thanks,  
Max

---

<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:** [February 28, 2021, 11:37am UTC](https://devforum.zoom.us/t/how-to-encode-email-for-users-userid-meetings-endpoint/41627/7 "2021-02-28T11:37:43Z")

</div>

Closed on February 28, 2021, 11:37am UTC

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