Connections Beta

A connection syncs messages between channels, usually a Slack channel and a Microsoft Teams channel. Each channel in a connection is an endpoint. The requests on this page list, create, repair and remove connections, and change the settings of each side.

The API creates Internal connections, between channels of your own organization. External and Bridge connections start with an invitation in the Dashboard. The API can read them, change your side, repair them and remove them.

Who can change connections

Reading needs the scope connections:read. Every change needs connections:readwrite.

The person the token acts for needs a permission from Admin console > Users and access > Roles & permissions :

For each channel, the person must be a full member of its workspace or team. Guests don’t count. For a private channel, the person must also be a member of the channel. A connection is visible when the person can access at least one of its endpoints.

A key that acts as Conclude follows extra rules:

• It holds the permissions above through its scopes.
• It only reaches channels that Conclude reaches. Those are public channels, and private channels that Conclude was added to.
• Every change needs a token with a subject. Without one, Conclude answers subject_required.

On an External or Bridge connection, you can change and remove only your own organization’s endpoints.

The connection object

{
  "id": "Y-7f9h1j3l",
  "type": "channel",
  "settings": {},
  "endpoints": [
    {
      "orgID": "O-2a4c6e8g",
      "teamID": "T-4c6e8g0i",
      "channelID": "C-6e8g0i2k",
      "sysChannelID": "C07ABCDEF12",
      "status": "ok",
      "settings": {"syncBotMessages": true},
      "created": "2026-10-27T14:03:12.52Z",
      "teamName": "Example",
      "channelName": "it-help",
      "platform": "slack",
      "url": "https://example.slack.com/archives/C07ABCDEF12"
    },
    {
      "orgID": "O-2a4c6e8g",
      "teamID": "T-8h0j2l4n",
      "channelID": "C-9i1k3m5o",
      "sysChannelID": "19:a1b2c3@thread.tacv2",
      "status": "ok",
      "settings": {},
      "created": "2026-10-27T14:03:12.52Z",
      "teamName": "IT",
      "channelName": "Help",
      "platform": "teams",
      "url": "https://teams.microsoft.com/l/channel/19%3Aa1b2c3%40thread.tacv2/Help"
    }
  ],
  "lastActivity": "2026-10-27T15:20:00Z",
  "created": "2026-10-27T14:03:12.52Z",
  "modified": "2026-10-27T14:03:12.52Z"
}

The endpoint object

Endpoint settings

Each endpoint has its own settings. Most of them decide what this side sends to the others.

The two attachment policies take effect only when an admin has turned on Allow channel-level overrides. Otherwise the organization’s policy applies. See File and image sharing.

Status

Each endpoint has a status. Conclude checks connections regularly and updates it.

When an endpoint stays broken, Conclude stops syncing it and sets disabled to true. That happens after seven days, or after two hours for corrupt. A disabled endpoint neither sends nor receives messages. It turns itself back on once Conclude finds it healthy.

List connections

GET /v1/connections · scope connections:read

Returns every connection with an endpoint in your organization that the token can see. The response is an array of connection objects, sorted by their first endpoint. It is not paged.

curl https://api.conclude.io/v1/connections -H "Authorization: Bearer $ACCESS_TOKEN"

Get a connection

GET /v1/connections/{connection} · scope connections:read

Returns one connection object.

Create a connection

POST /v1/connections · scope connections:readwrite

Connects two or more channels of your organization. Conclude marks the channels as connected and starts to sync them. The audit log records connect.channel.created.

curl https://api.conclude.io/v1/connections \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"type": "channel", "endpoints": [{"channelID": "C-6e8g0i2k"}, {"channelID": "C-9i1k3m5o"}]}'

The response is the new connection object.

Delete a connection

DELETE /v1/connections/{connection} · scope connections:readwrite

Deletes the connection and stops syncing all its channels. On an External connection, this also removes the other organization’s side. On a Bridge connection, it disconnects the channels from the bridge. The response is 200 with an empty body.

A key can delete an External or Bridge connection only when at most one of its endpoints belongs to another organization. Otherwise, remove your own endpoints.

Repair a connection

POST /v1/connections/{connection}/repair · scope connections:readwrite

Checks every endpoint and fixes what Conclude can fix. It reads each channel again from Slack or Microsoft Teams. It renews Conclude’s subscriptions to the channels’ messages. In Microsoft Teams, it also adds Conclude’s integration account to a private or shared channel again. Then it checks the endpoints once more and updates their status.

The request has no body. Repair runs while you wait, so it can take several seconds. The response is the connection object with the new status of each endpoint.

Repair can’t fix every status. See Status for what to do. If an endpoint has been broken longer than its grace period, repair disables it, and Conclude alerts your admins.

Add an endpoint

POST /v1/connections/{connection}/endpoints · scope connections:readwrite

Adds a channel of your organization to an Internal connection.

curl https://api.conclude.io/v1/connections/Y-7f9h1j3l/endpoints \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"channelID": "C-0j2l4n6p"}'

The response is the connection object with the new endpoint.

Remove an endpoint

DELETE /v1/connections/{connection}/endpoints/{channel} · scope connections:readwrite

Removes a channel of your organization from the connection. {channel} is the channel’s Conclude ID.

When fewer than two endpoints remain, Conclude deletes the whole connection. The response is then the connection with an empty endpoints list. Removing either side of a Bridge connection disconnects both. Otherwise the response is the connection object without the removed endpoint.

Change endpoint settings

PUT /v1/connections/{connection}/endpoints/{channel}/settings · scope connections:readwrite

Replaces the settings of one of your organization’s endpoints. The body is the settings object. A field you leave out goes back to its default. Leaving out owner keeps the current owner, and inviter never changes.

To change one setting, read the connection first, change the setting and send all the settings back.

curl -X PUT https://api.conclude.io/v1/connections/Y-7f9h1j3l/endpoints/C-6e8g0i2k/settings \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"syncBotMessages": true, "translate": "de"}'

The response is the endpoint object with its new settings.