It was indeed not necessary to have the _uid.

Well deserved - kudos!

@baris I have it working - I just needed to use a user token that was not the master and add the _uid=0 to as param..

endpoints are present:

   setupApiRoute(router, 'put', '/:cid/watch', [...middlewares, middleware.assert.category], controllers.write.categories.setWat>
    setupApiRoute(router, 'delete', '/:cid/watch', [...middlewares, middleware.assert.category], controllers.write.categories.set>

Yields 404 also.
Can I, in the administration Dashboard, see if I'm running on the "develop" branch?
From serverside, I can check with git status where it clearly states I'm running on that branch but from the dashboard.

@baris Through Postman - I can share the request if you have the time; otherwise, here is a screenshot of the Postman configuration:

@julian, thanks for the update.
"The other issue is that the top of the docs always says "3.0.0", which isn't quite correct. It's hardcoded currently."
This will be the dot above the I to make it more correct; in this case, I assume, 3.5.1.

I have deployed a version from the "develop" branch, which states 3.5.1 in the administration dashboard.
Shouldn't this also state something differently to make it differ from the production branches?

I'm still getting a 404 error with the watch API endpoint in this case:
"https://nodebb.dangdi.life/api/v3/categories/2/watch"
with the body:
{
"uid": 2,
"state": "watching"
}

Should I run a different branch?

@baris thank you for pointing me at the solution.
I think it would be a good idea that the official API docs follows the latest release branch instead of dev

Thanks for the update, @julian - I might be getting too old, but following the documentation, it does not seem to work on our latest deployment of 3.5.1.
Here is my Postman setup. Maybe you can spot my wrongdoings

@julian Talk about good timing - thank you for the effort and an amazing product!

I don't see the functionality in the write API - did I not search in the right place or is it in the TODO list?

Thanks for the quick answer, @baris!
Regarding how it works in the front end:
If the user has permission to system tags, they will appear when entering the tag name (suggest search).
The system tags will not be visible to users that don't have permission.

Can system tags be used in the API?