# Update Meeting - enable send reminder email?

**URL:** <https://devforum.zoom.us/t/update-meeting-enable-send-reminder-email/53862>\
**Category:** API and Webhooks\
**Created:** [July 8, 2021, 5:10pm UTC](https://devforum.zoom.us/t/update-meeting-enable-send-reminder-email/53862 "2021-07-08T17:10:41Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![sharoniab](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/sharoniab/32/11892_2.png) [@sharoniab](https://devforum.zoom.us/u/sharoniab)\
**Post date:** [July 8, 2021, 5:10pm UTC](https://devforum.zoom.us/t/update-meeting-enable-send-reminder-email/53862/1 "2021-07-08T17:10:41Z")

</div>

## Using this template helps us debug your issues more effectively 🙂

**Description**  
I am updating a meeting through the API, if a user is changing the name or date of a meeting through a linked event management system. I can’t figure out how to trigger a ‘meeting updated’ reminder email to existing registrants when the update occurs through the API. When in the Zoom interface, if I edit an existing meeting that has registrants, I get a dialog box with “Notify registrants about changes to this meeting” checked by default. However when I make the same update through the API, I can’t find a query parameter or setting to default-send the notification email. When I test the update through the API it does not trigger the email, even when I’m making critical changes to the meeting that registrants need to know about, such as a date change.

I see that the DELETE /meetings/{meetingId} endpoint has a query parameter cancel\_meeting\_reminder, but nothing similar for PATCH /meetings/{meetingId}. Is there a way to achieve this?

**Which Endpoint/s?**  
[patch] /meetings/{meetingId}

---

<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:** [July 9, 2021, 4:48pm UTC](https://devforum.zoom.us/t/update-meeting-enable-send-reminder-email/53862/2 "2021-07-09T16:48:58Z")

</div>

Hi @sharoniab,

Thanks for reaching out about this. I believe that if the following field is set to true for a meeting scheduled via API, an email should go out for updates as well:  
 ![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/1/a/1acb53d91f5c6960f60923ef3e67b128a8fb2560.png)

Are you seeing otherwise on your end? Let me know and I’ll be happy to further assist.

Thanks!  
Will

---

<div class="post-metadata">

**Author:** ![sharoniab](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/sharoniab/32/11892_2.png) [@sharoniab](https://devforum.zoom.us/u/sharoniab)\
**Post date:** [July 9, 2021, 9:18pm UTC](https://devforum.zoom.us/t/update-meeting-enable-send-reminder-email/53862/3 "2021-07-09T21:18:17Z")

</div>

Hi @will.zoom, thanks for your reply.

The meeting already had this field set to true during setup:  
“registrants\_confirmation\_email”: true

But I don’t know if there is any field specific to an ‘update email’ to registrants. I tested again and noted that for an individual meeting, the email was sent on update. It was for a recurring meeting where I updated one of the occurrences via the API, that did NOT send an email update to registrants for either the recurrence or the overall series. That recurring meeting also had “registrants\_confirmation\_email”: true.

---

<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:** [July 12, 2021, 9:02pm UTC](https://devforum.zoom.us/t/update-meeting-enable-send-reminder-email/53862/4 "2021-07-12T21:02:08Z")

</div>

Hi @sharoniab,

Thank you for confirming—I just sent you a private message for some more details so that I can look into this further for you.

Thanks,  
Will

---

<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:** [July 14, 2021, 3:12pm UTC](https://devforum.zoom.us/t/update-meeting-enable-send-reminder-email/53862/5 "2021-07-14T15:12:57Z")

</div>

Hi @sharoniab,

Thank you for sharing that with me.

In doing some further testing from my end, I can confirm I’m experiencing the same behavior when updating a single occurrence of a recurring meeting with registration required and confirmation email settings set to true.

I’ve gone ahead and raised this with our Engineering team, as I can definitely appreciate the concern you’ve raised here (ZOOM-292397).

I will follow up here with updates as I have them.

Thanks!  
Will

---

<div class="post-metadata">

**Author:** ![sharoniab](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/sharoniab/32/11892_2.png) [@sharoniab](https://devforum.zoom.us/u/sharoniab)\
**Post date:** [July 14, 2021, 8:44pm UTC](https://devforum.zoom.us/t/update-meeting-enable-send-reminder-email/53862/6 "2021-07-14T20:44:08Z")

</div>

Thanks Will, appreciate it.

---

<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:** [July 15, 2021, 2:31pm UTC](https://devforum.zoom.us/t/update-meeting-enable-send-reminder-email/53862/7 "2021-07-15T14:31:55Z")

</div>

No problem, @sharoniab — I hope to be in touch about this shortly.

Best,  
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:** [August 15, 2021, 12:32am UTC](https://devforum.zoom.us/t/update-meeting-enable-send-reminder-email/53862/8 "2021-08-15T00:32:09Z")

</div>

Closed on August 15, 2021, 12:32am UTC

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