I see discussion about setting notification_level via the API. What about reading values? For example, I can set a value with: PUT {{base_url}}/category/14/notifications.json?api_key={{api_key}}&api_username={{api_username}}&notification_level=3 How can I read that same value back?

Normally reversing out the API has worked for me, but for some reason this time I don’t see it. From a user’s profile page (/u/user_name/summary) I see the /u/user_name/summary.json payload, but don’t see anything in there about notification_level’s there. Clicking on the Preferences tab loads /us…

A GET to https://meta.discourse.org/categories.json contains: { "category_list": { "categories": [ { "notification_level": 1, ... }, ] } }

It finally occurred to me: /categories.json > notification_level is for the logged in user. I took that to be the default notification_level for the category, which of course categories don’t have. Thanks, @Falco !

So … by this approach, that means getting a given user’s /categories.json > notification_level requires this update to the client object? client.api_username = @each_users_username One cannot just do something like so without changing the client.api_username value?: client.categories(api_username…

API GET para notificación_level de usuario de categoría

Desarrollador

sam (Sam Saffron) 21 Febrero, 2019 07:47 2

Have a look at Reverse engineer the Discourse API visit your profile page on the tab that shows it, its in one of the user json payloads.

Tema		Respuestas	Vistas
API for Category based notification level update Development	9	2424	30 Octubre 2017
Data Explorer - list of notification status per category Data & reporting sql-query	3	503	26 Julio 2021
Change notification level with a link Feature notifications	11	2566	29 Enero 2026
Notification levels - understanding and communicating category notification levels Support notifications	10	5128	10 Julio 2023
Discourse Notifier Plugin	8	2447	13 Febrero 2022

API GET para notificación_level de usuario de categoría

Temas relacionados