We’re deploying an update to the Communities APIs to have OAuth scopes rather than the current, loosely-defined OAuth scopes. In that, we’re removing the create endpoint as well. We will be producing new documentation ASAP. Here are the changes:
Adding new OAuth scopes: communities_edit communities_moderate
Remove Create a Community endpoint.
Update Community now requires the communities_edit scope.
Get Community Banned Users requires the communities_moderate scope.
Ban/Un-ban Community User now requires the communities_moderate scope.
Create/Delete Community Avatar/Cover Image now requires the communities_edit scope.
Get/Add/Delete Community Moderator now requires communities_edit scope.
Get/Add/Delete Community Timed-Out Users now requires the communities_moderate scope.
Set/Delete Channel Community now requires the channel_editor scope.
Let me know if you have questions! Sorry for the change inside of the same version. We’re trying to minimize this as much as possible, but we thought this was a necessary change.
Good question, @BarryCarlyon. An application can get the _moderate scope for any moderators inside a community. The _edit scope is for the community owner only.
Just for clarification, Get bans will also require communities_moderate? Also, Get Community Moderators doesn’t seem to require the communities_edit scope you mentioned, I’m able to get a mod list without including any token so what’s the intended behaviour?