Skip to:
Content

BuddyPress.org

Opened 10 months ago

Last modified 7 weeks ago

#8774 new enhancement

Add ability to change Email notification settings via REST API

Reported by: niftythree's profile niftythree Owned by:
Milestone: Up Next Priority: normal
Severity: normal Version: 10.6.0
Component: REST API Keywords: needs-patch
Cc:

Description

Hi,

We have an app in which members sometimes have lengthy private message conversations; some members may have 300+ messages within a single thread. We will be utilising Firebase notifications to send app users notifications of new private messages. The combination of Firebase notifications and email notices means that app users get multiple notifications of each new private message. We could disable the email notices, however, we also have a cohort of users who only use our website, and therefore rely on the email notices.

If possible, it would be great to have the ability to allow app users to update their email notice/notification settings through the REST API. This would also allow us to set email notifications off by default for users who log in through the app (but users could then turn it back on, if they wish). This would be more convenient for app users, but also would also reduce the volume of emails going out, keeping email providers happier.

Please let us know if the ability to do this already exists and we've overlooked it.

Thanks.

Change History (4)

#1 @espellcaste
9 months ago

  • Milestone changed from Awaiting Review to Up Next

#2 @imath
9 months ago

  • Milestone changed from Up Next to 12.0.0

#3 @imath
8 weeks ago

  • Keywords needs-patch added
  • Milestone changed from 12.0.0 to Up Next

Hi @niftythree

It doesn't exist, but I believe we should do it. I've opened an issue on the BP REST GitHub repository: https://github.com/buddypress/BP-REST/issues/488

Let's try to implement it during next release. (sorry we didn't find the time during 12.0 dev. cycle).

#4 @niftythree
7 weeks ago

Thanks for the update, @imath.
Thanks to all for the continued work. 🙂

Note: See TracTickets for help on using tickets.