Correct scope for Set Notification Level API endpoint: Users are discussing the correct scope for the Set Notification Level API endpoint to limit an API key to set the notification level on a given topic for any user. Gooman initiated the discussion, and aidanheerdegen shared similar concerns about setting notification levels for important topics. JammyDodger provided a solution, referencing the /t/<topic_id>/notifications endpoint, which allows admins with global scope to change another user’s notification level via a POST request with parameters username or external_id and notification_level.
What’s the correct scope to limit an API Key to just the Set Notification Level endpoint?
My external service needs to set the notification level on a given topic, for any given user. So I guess I need User Level to be All Users, Scope as Granular - but the (?) help on the page doesn’t give any direction as to which scope is concerned with notification levels.
Can someone help?
I’d like to know this too. We have a lot of problem getting people watching important topics that we use as mailing lists. We’d like to either do it for them, or have a few big buttons they could push to watch important topics.
I think you can now use the /t/<topic_id>/notifications endpoint for this:
Thanks for the prompt reply.