Hi, I’ve spent several hours trying to update users email preferences via the api, and haven’t had much luck. Specifically, I want to enable Activity Summary and turn of Mailing list mode. Has anyone done this and succeeded and can point me at where I’ve gone wrong? Some examples below. I tried this with and without the user/user option layers. Unfortunately there isn’t a meaningful error, just a page of html spat out. $ curl -X POST --data ‘user: { user_option: {“mailing_list_mode_frequency”: 1, “email_direct”: True, “mailing_list_mode”: False, “email_digests”: True, “email_in_reply_to”: True, “enable_quoting”: True, “like_notification_frequency”: 1, “email_always”: True, “email_private_messages”: True, “email_previous_replies”: 1, “include_tl0_in_digests”: True}}}’ “https://discuss.example.com/users/karl_goetz?api_key=[..]&api_username=karl_goetz” Forums Using pydiscuourse (installed from pip), has also failed. Some examples of me finding with the options: discourse_client.set_preference(mailing_list_mode=False, email_digests=True, email_direct=True, email_in_reply_to=True, email_private_messages=True, digest_after_minutes=1440, include_tl0_in_digests=True) discourse_client.set_preference(‘karl_goetz’, email_always=True, mailing_list_mode=False, email_digests=True, email_direct=True, email_in_reply_to=False, email_private_messages=True, email_previous_replies=1, digest_after_minutes=1440, include_tl0_in_digests=True) I can change my user preferences via chrome at example.com/u/karl_goetz/preferences/emails so that bit works and if nothing else I’ll try pushing data in through that route.

You will need to send a PUT request to /u/{{username}}.json email_always:true mailing_list_mode:false mailing_list_mode_frequency:1 email_digests:true email_direct:true email_in_reply_to:true email_private_messages:true email_previous_replies:2 digest_after_minutes:10080 include_tl0_in_digests:false

Thanks @blake, I think that has me back on the right path. curl -X PUT “https://discuss.example.com/u/karl_goetz.json?api_key=[...]&api_username=karl_goetz&mailing_list_mode=false&email_digests=true” Now when I refresh the web my settings have changed from mailing list mode to activity summary. After more annoyance and reporting to reading the pydisuourse source it appears the _PUT method doesn’t support passing params so I used their _request method directly. d {‘email_always’: ‘true’, ‘mailing_list_mode_frequency’: 1, ‘email_private_messages’: ‘true’, ‘email_direct’: ‘true’, ‘mailing_list_mode’: ‘false’, ‘digest_after_minutes’: 1440, ‘email_digests’: ‘true’, ‘include_tl0_in_digests’: False, ‘email_in_reply_to’: ‘true’, ‘email_previous_replies’: 1, ‘api_username’: ‘karl_goetz’, ‘api_key’: ‘[…]’} discourse_client._request(‘PUT’, ‘/u/karl_goetz.json’, params=d) Which behaved as expected. Thanks again for your assistance. PS. Do you know why some user settings are only accessible via /u/username not /users/username ?

At some point we renamed the /users endpoint to /u so that we can have pretty short urls in the browser like we do for topics and categories. If you do $ rake routes | grep username you will see most of the routes and I think currently most of the /users ones have duplicate /u routes. The line is generating the /u routes: config/routes.rb main get "robots" => "robots_txt#show" put "robots.json" => "robots_txt#update" delete "robots.json" => "robots_txt#reset" resource :email_style, only: %i[show update] get "email_style/:field" => "email_styles#show", :constraints => { field: /html|css/ } end resources :embeddable_hosts, only: %i[create update destroy], constraints: AdminConstraint.new resources :color_schemes, only: %i[index create update destroy], constraints: AdminConstraint.new resources :permalinks, only: %i[index create show update destroy], constraints: AdminConstraint.new scope "/customize" do resources :watched_words, only: %i[index create destroy] do collection do get "action/:id" => "watched_words#index" get "action/:id/download" => "watched_words#download" but I believe there are still some /users routes that don’t have a matching /u route.

Updating email preferences via API

Product Support

codinghorror (Jeff Atwood) July 15, 2017, 12:31am 5

We should figure out what those are, and fix them so the /u works as expected..

Topic		Replies	Views
Changing a user's email address via api Development rest-api	7	2316	March 14, 2016
Unsubscribing a user from all emails via an API call? Product Support	5	1360	September 23, 2020
Edit a user preference for everyone or a subset of users Self-Hosting how-to	0	14330	February 12, 2015
Default email settings for a new user Feature email	42	12107	August 21, 2015
Bulk change user settings Product Support	1	1674	March 31, 2017

Updating email preferences via API

Related topics