Create a community channel

Create a channel inside one of the creator's community groups — get a group id from the create-channel-group endpoint, or an existing one from the list-channel-groups endpoint. A channel belongs to exactly one group through this API.

mangoes/badges decide who can actually access the channel; visibility decides who can even see that it exists — these are independent settings. At least one of mangoes or badges must be given — there is no "open to everyone" option at creation, matching the creator dashboard's own rule.

communityProfilePicture accepts either a fresh image URL (type image) or a plain emoji character (type emoji) — a fresh image URL doesn't need to already be a previously-uploaded asset; it's registered automatically.

Fails with a 400 if name is missing or empty, if group is missing, if features is missing or empty, if both mangoes and badges are empty, if any id appears in both mangoes and excludeMangoes (or both badges and excludeBadges), or if communityProfilePicture is given without communityProfilePictureType. Fails with a 400 if the Community feature is not enabled for this creator. Fails with a 404 if group, or any mango/badge id in mangoes/badges/excludeMangoes/excludeBadges, does not belong to this creator.

Authorization

bearer

AuthorizationBearer <token>

In: header

Header Parameters

x-whitelabel-host*string

Host name of the dashboard, ex: mydomain.tagmango.com

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

name*string

Name of the channel — shown as its label in the community sidebar and at the top of its feed/chat.

description?string

Description of the channel — shown to members under its name, explaining what it's for. The creator dashboard's own create flow never actually lets a creator set this (there's no field for it in that UI), so most existing channels have it blank — treat it as a nice-to-have, not something partners need to always fill in. Defaults to an empty string.

Default""

group*object

Id of the group this channel belongs to. Must already exist and belong to this creator — get one from the create-channel-group endpoint, or an existing id from the list-channel-groups endpoint. A channel belongs to exactly one group through this API — the dashboard's own create flow allows several, but this endpoint intentionally narrows that to one.

mangoes?array<>|

Mangoes (paid services) whose active subscribers can access this channel. This is separate from visibility — visibility only controls who can see that the channel exists; actual access always comes from here or badges. At least one of mangoes or badges must be non-empty — there is no "open to everyone" option at creation; a request where both are empty is rejected with a 400, matching the creator dashboard's own rule. Defaults to an empty array if omitted; an explicit null is treated the same as omitting it, not as an error.

Default[]

badges?array<>|

Badges whose holders can access this channel. See mangoes — at least one of mangoes or badges must be non-empty, or the request is rejected. Defaults to an empty array if omitted; an explicit null is treated the same as omitting it.

Default[]

excludeMangoes?array<>|

A member with an active subscription to any mango in this list is blocked from the channel, independent of mangoes/badges — exclusion is checked directly against the member's own subscriptions, not against whatever granted them access, so it blocks them even if they separately qualify some other way. Must not share any id with mangoes — a mango cannot be both included and excluded at once.

excludeBadges?array<>|

A member holding any badge in this list is blocked from the channel, independent of mangoes/badges — exclusion is checked directly against the member's own badges, not against whatever granted them access, so it blocks them even if they separately qualify some other way. Must not share any id with badges — a badge cannot be both included and excluded at once.

visibility*string

Who can see that the channel exists. public: every community member sees it in the sidebar, but only those with real access (per mangoes/badges) can open it — shown locked to everyone else. members_only: only members with access can see it at all. hidden: nobody but the creator can see or open it, regardless of mangoes/badges.

Value in"public" | "hidden" | "members_only"

features*array<>

What capabilities the channel has, as an array — combine both to give it everything. At least one is required; a channel with neither would be unusable, so unlike the internal dashboard flow (which allows an empty array), this endpoint rejects it outright. feed: turns on the channel's post feed — members with access can view posts, and (only if featureSettings.feed.allowMemberPosts is also true) post into it themselves; otherwise only the creator posts. messages: turns on the channel's chat — whether members can actually send anything is controlled separately by featureSettings.messages.

Items1 <= items

communityProfilePicture?string

The channel's icon, shown next to its name in the sidebar. Required together with communityProfilePictureType, which says how to interpret this value.

communityProfilePictureType?string

Says how to interpret communityProfilePicture. Required if it's given, ignored otherwise. image: communityProfilePicture is an image URL — it doesn't need to already be a previously-uploaded TagMango Cloud asset; a fresh URL is registered automatically the first time it's used. emoji: communityProfilePicture is a single emoji character (e.g. "🎉"), rendered directly as the icon — no upload involved.

Value in"emoji" | "image"

featureSettings?

Fine-grained, per-feature settings — a container for feed and messages, each only meaningful when the matching value is present in features. These control what members can do (post, message, share); they don't restrict the creator, who can always post and message regardless of these settings. Omitting this whole object, or either key under it, leaves every setting inside off — it never falls back to "on." Note this endpoint is more capable than the creator dashboard here: the dashboard's own create flow always creates a channel with every one of these settings locked to false and only lets a creator loosen them afterward, one at a time, from the channel's edit screen — this endpoint lets you set the real values directly at creation time.

Response Body

`application/json`

curl -X POST "https://api-prod-new.tagmango.com/api/v1/external/community/channel-groups/channels" \  -H "x-whitelabel-host: string" \  -H "Content-Type: application/json" \  -d '{    "name": "General",    "group": "61e97c146cf2b4d8c68f3a40",    "visibility": "public",    "features": [      "feed"    ]  }'

{
  "creator": "61e97c146cf2b4d8c68f3a41",
  "visibility": "public",
  "communityProfilePicture": "https://example.com/image.jpg",
  "communityProfilePictureType": "image",
  "featureSettings": {
    "feed": {
      "allowMemberPosts": true
    },
    "messages": {
      "allowEveryoneToMessage": true,
      "allowPeerToPeerMessaging": true,
      "sharingControlSettings": {
        "allowFileSharing": true,
        "allowPhotoSharing": true,
        "allowVideoSharing": true,
        "allowAudioSharing": true,
        "allowPollSharing": true
      }
    }
  },
  "chatRoom": "61e97c146cf2b4d8c68f3a44",
  "_id": "61e97c146cf2b4d8c68f3a40",
  "name": "General",
  "description": "General discussion for all members",
  "features": [
    "feed"
  ],
  "archived": false,
  "createdAt": "2026-01-01T00:00:00.000Z",
  "updatedAt": "2026-01-01T00:00:00.000Z",
  "mangoes": [],
  "badges": [],
  "excludeMangoes": [
    "string"
  ],
  "excludeBadges": [
    "string"
  ],
  "groups": [
    "61e97c146cf2b4d8c68f3a40"
  ]
}

{
  "code": 400,
  "type": "Bad Request",
  "statusMessage": "BAD_REQUEST",
  "success": false,
  "message": "Invalid request",
  "result": "Invalid request"
}

{
  "code": 401,
  "type": "Unauthorized",
  "statusMessage": "UNAUTHORIZED",
  "message": "Invalid token",
  "result": "Invalid token",
  "success": false
}

{
  "code": 403,
  "type": "Forbidden",
  "statusMessage": "FORBIDDEN",
  "errorCode": "WORKSHOP_MANGO_FORBIDDEN",
  "message": "You can not access this api with a TagMango account, only available for whitelabel hosts",
  "result": "You can not access this api with a TagMango account, only available for whitelabel hosts",
  "success": false
}

{
  "code": 429,
  "type": "Too Many Requests",
  "statusMessage": "TOO_MANY_REQUESTS",
  "message": "Request limit exceeded. try after 10 seconds",
  "result": "Request limit exceeded. try after 10 seconds",
  "success": false
}

Create a community channel

Authorization

Header Parameters

Request Body

Response Body

201application/json

400application/json

401application/json

403application/json

429application/json

`application/json`

`application/json`

`application/json`

`application/json`

`application/json`