Correct scope for Set Notification Level API endpoint

[Gooman (David Gurr)]

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?

[aidanheerdegen]

@Gooman

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.

[JammyDodger]

I think you can now use the /t/<topic_id>/notifications endpoint for this:

@AlexDev

Some details about this API endpoint that are important to note:

• The API user should be an admin(so they should have global scope) to be able to change another user’s notification level.
• Endpoint URL: siteurl/t/<topic_id>/notifications
• Request type: POST
• Parameters:
  • username or external_id of the target user. If empty, the admin’s own notifcation level for the topic will be changed.
  • notification_level: integer value corresponding to the level
    • muted: 0,
    • regular: 1,
    • normal: 1, # alias for regular
    • tracking: 2,
    • watching: 3,

[aidanheerdegen]

Thanks for the prompt reply.