Community structure

Channel and group management. Community content — posts, comments, chat — lives on the Community API. All routes require a Authorization: Bearer header — see Authentication.

Create a channel

curl -X POST "https://example.com/communities/string/channels" \  -H "Content-Type: application/json" \  -d '{    "name": "string",    "type": "feed"  }'

{  "channel": {    "id": "string",    "name": "string",    "type": "feed",    "groupId": "string",    "description": "string",    "readonly": true,    "access": "inherit"  }}

{  "error": "string",  "message": "string"}

Create a channel group

curl -X POST "https://example.com/communities/string/groups" \  -H "Content-Type: application/json" \  -d '{    "name": "string"  }'

{  "group": {    "id": "string",    "name": "string",    "description": "string"  }}

{  "error": "string",  "message": "string"}

Update a channel

curl -X PATCH "https://example.com/communities/string/channels/string" \  -H "Content-Type: application/json" \  -d '{}'

{  "channel": {    "id": "string",    "name": "string",    "type": "feed",    "groupId": "string",    "description": "string",    "readonly": true,    "access": "inherit"  }}

{  "error": "string",  "message": "string"}

Delete a channel

curl -X DELETE "https://example.com/communities/string/channels/string"

{  "channelId": "string"}

{  "error": "string",  "message": "string"}

Update a group

curl -X PATCH "https://example.com/communities/string/groups/string" \  -H "Content-Type: application/json" \  -d '{}'

{  "group": {    "id": "string",    "name": "string",    "description": "string"  }}

{  "error": "string",  "message": "string"}

Delete a group

curl -X DELETE "https://example.com/communities/string/groups/string"

{  "groupId": "string"}

{  "error": "string",  "message": "string"}

Reorder or re-parent a channel/group

curl -X POST "https://example.com/communities/string/move-node" \  -H "Content-Type: application/json" \  -d '{    "nodeType": "channel",    "nodeId": "string",    "positionMode": "into-group"  }'

{  "communityId": "string"}

{  "error": "string",  "message": "string"}

Community API (management routes)

Members, roles, settings, calendar events and the moderation queue live on the Community API — base URL https://api.zanfia.com/community, routes below are relative to it. They are not part of the Workspace API spec above. Workspace keys need the communities:read / communities:write scopes and pass as staff; member keys are admitted by the guard, but every group requires the community permission listed next to it, so a plain member key gets 403 insufficient-permissions. Ids in the path: communityId from GET /v1/communities; memberId is the member doc id from the member list.

Members (manageMembers; mute needs muteMembers)

Roles (manageRoles)

Settings (manageCommunity)

Accepted patch keys: uploadVideo, membersDisplay, viewStyle, displayName, icon, hiddenWhenUnavailable, voiceMessages, enableMemberApiAccess, publicAccess, publicAccessTermsUrl, contentVisibleFromJoinDate, eventsEnabled, directMessagesEnabled, gamification, moderation, assistant, digest. Nested blocks replace their whole sub-object:

{
  "patch": {
    "eventsEnabled": true,
    "directMessagesEnabled": true,
    "contentVisibleFromJoinDate": false,
    "gamification": { "enabled": true },
    "moderation": { "autoHideAfterReports": 3 }
  }
}

Calendar events (manageCommunity)

startAt / endAt are ISO 8601 instants; timezone is the IANA zone the event was authored in (Europe/Warsaw). type is one of liveCall, workshop, meetup, conference, retreat, other (default). End must be after start and an event may span at most 31 days — 400 invalid-time-range. Unknown event → 404 event-not-found. Events only show to members while eventsEnabled is on in the settings.

Moderation queue (moderatePosts or moderateComments)

One report per reported target (id is {targetType}_{targetId}); reporters lists who flagged it and why, autoHidden tells you the report threshold already hid the content. remove soft-deletes the post/comment and notifies its author (the note is included); dismiss keeps it and restores an auto-hidden target. Resolving a post report needs moderatePosts, a comment report moderateComments. 404 report-not-found, 409 report-already-resolved on a second verdict.