Chats Beta

A chat is a private conversation between named people across Slack and Microsoft Teams. Conclude creates a private Slack channel and a Microsoft Teams group chat, and syncs them. The requests on this page list, start, change and close chats.

A chat within your organization has a channel in your Slack workspace and one in your Microsoft Teams tenant. A chat with people of another organization runs over a Bridge. It has a channel in each organization, and the API shows only yours. Cross-platform chats describes how chats work in Slack and Microsoft Teams.

Who can use chats

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

Only a chat’s members can see it. The requests on this page act for the person the token acts for:

• A key that acts as you reaches your chats
• A key that acts as Conclude, with a subject, reaches the subject’s chats
• A key that acts as Conclude, without a subject, reads every chat with a channel in your organization. It can also start chats between the people it names. To change, check or delete a chat, it needs a subject. Without one, Conclude answers subject_required
• For anyone else who is not a member, a chat doesn’t exist. Conclude answers not_found

Starting, changing and deleting a chat within your organization needs the Create chats permission from Admin console > Users and access > Roles & permissions . For a key that acts as Conclude, the scope chats:readwrite stands in for it.

A chat with another organization uses the bridge’s Chat access list instead of the Create chats permission. Everyone in the chat must be on that list, including the person the token acts for. Each organization manages its own list, so no scope can replace it. Any member of the chat can close it.

The chat object

{
  "id": "Y-7f9h1j3l",
  "topic": "Laptop refresh",
  "autoName": true,
  "status": "ok",
  "lastActivity": "2026-11-05T09:12:44Z",
  "myChannelID": "C-6e8g0i2k",
  "channels": [
    {
      "id": "C-6e8g0i2k",
      "name": "chat_ana_ben",
      "platform": "slack",
      "sysID": "C07ABCDEF12",
      "workspace": {
        "id": "T-4c6e8g0i",
        "name": "Example",
        "sysID": "T04ABCDEF12"
      },
      "url": "slack://channel?team=T04ABCDEF12&id=C07ABCDEF12"
    },
    {
      "id": "C-9i1k3m5o",
      "name": "Chat between Ana and Ben",
      "platform": "teams",
      "sysID": "19:a1b2c3d4@thread.v2",
      "workspace": {
        "id": "T-8h0j2l4n",
        "name": "Example",
        "sysID": "8f0e2d4c-6b8a-4c2e-9f1d-3b5a7c9e1f20"
      },
      "url": "https://teams.microsoft.com/l/chat/19:a1b2c3d4@thread.v2"
    }
  ],
  "members": [
    {
      "id": "U-2b4d6f8h",
      "mention": "Ana",
      "name": "Ana Silva",
      "email": "ana@example.com",
      "avatar": "https://avatars.example.com/ana.png",
      "orgID": "O-2a4c6e8g"
    },
    {
      "id": "U-3b5d7f9h",
      "mention": "Ben",
      "name": "Ben Okafor",
      "email": "ben@example.com",
      "orgID": "O-2a4c6e8g"
    }
  ]
}

The chat channel object

A chat’s channel is a private Slack channel or a Microsoft Teams group chat.

The user object

Status

Any other value is the status of the first broken channel, such as noAuth or deactivated. The Connections page says what to do about each.

List chats

GET /v1/chats · scope chats:read

Returns a page of chats, newest first by when they were created. It includes chats with other organizations, and leaves out chats on a bridge that an admin has paused.

curl -G https://api.conclude.io/v1/chats \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  --data-urlencode "bridge=none"

To read the next page, send the same request with position set to nextPosition. URL-encode the value.

Get a chat

GET /v1/chats/{chat} · scope chats:read

Returns one chat object.

curl https://api.conclude.io/v1/chats/Y-7f9h1j3l -H "Authorization: Bearer $ACCESS_TOKEN"

Start a chat

POST /v1/chats · scope chats:readwrite

Starts a chat between the person the token acts for and the people you name. Conclude creates a private Slack channel and a Microsoft Teams group chat and adds everyone to them. The audit log records connect.chat.created.

A key that acts as Conclude, without a subject, starts a chat between the people you name. Name at least two, and at least one from your organization. The first of them from your organization counts as the person who started the chat. The audit log names Conclude.

curl https://api.conclude.io/v1/chats \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"members": ["U-3b5d7f9h"], "topic": "Laptop refresh"}'

The response has these fields:

Slack and Microsoft Teams can take a few seconds to add everyone. Check the members to find people they didn’t add.

Chats with another organization

To chat with people of another organization, name your bridge with that organization in bridge. GET /v1/bridges lists your bridges, and GET /v1/bridges/{bridge}/chatUsers lists the people you can name. Everyone must have Chat access on the bridge, and at least one of them must be from the other organization. A key that acts as Conclude, without a subject, names at least two people. The first of them on your organization’s side of the Chat access list counts as the person who started the chat. The audit log records bridge.chat.created instead.

curl https://api.conclude.io/v1/chats \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"members": ["U-5e7g9i1k"], "bridge": "B-1a3c5e7g", "topic": "Renewal"}'

Without bridge, everyone you name must be a user in your organization, even someone who is on a bridge’s Chat access list.

Change a chat

PATCH /v1/chats/{chat} · scope chats:readwrite

Changes the chat’s topic, the name of its channels and its members, as one change. Slack and Microsoft Teams rename the channels at most once. A field you leave out stays as it is. Changes to one chat’s members run one at a time, so a request waits while another one changes the chat.

curl -X PATCH https://api.conclude.io/v1/chats/Y-7f9h1j3l \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"topic": "Laptop refresh, phase 2", "addMembers": ["U-4c6e8g0i"], "removeMembers": ["U-3b5d7f9h"]}'

The response has the changed chat object as chat, and the people Conclude didn’t add as skippedMembers, as when you start a chat. When autoName is true and the members changed, Conclude renames the channels after them. The audit log records connect.chat.updated when people joined or left, or the channels got a new name.

Add members

POST /v1/chats/{chat}/members · scope chats:readwrite

Adds people from your organization to the chat. People who are already members stay as they are. To add and remove people in one change, change the chat instead. Changes to one chat’s members run one at a time, so a request waits while another one changes the chat.

curl https://api.conclude.io/v1/chats/Y-7f9h1j3l/members \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"members": ["U-4c6e8g0i"]}'

The response has the changed chat object as chat, and the people Conclude didn’t add as skippedMembers, as when you start a chat. When autoName is true, Conclude renames the channels after the new members. The audit log records connect.chat.updated.

Remove a member

DELETE /v1/chats/{chat}/members/{user} · scope chats:readwrite

Removes a person from the chat. {user} is their user ID. The person the token acts for can’t remove themselves. Another member can, or they can delete the chat.

curl -X DELETE https://api.conclude.io/v1/chats/Y-7f9h1j3l/members/U-4c6e8g0i \
  -H "Authorization: Bearer $ACCESS_TOKEN"

The response has the changed chat object as chat. When autoName is true, Conclude renames the channels after the remaining members. The audit log records connect.chat.updated.

Check members

POST /v1/chats/{chat}/verify · scope chats:readwrite

Reads the members of each channel from Slack and Microsoft Teams again, and returns the members who are missing from a channel. The request has no body.

curl -X POST https://api.conclude.io/v1/chats/Y-7f9h1j3l/verify \
  -H "Authorization: Bearer $ACCESS_TOKEN"

{
  "missingMembers": []
}

missingMembers is a list of user objects. A member is missing when they are in the chat on one platform, but not in the channel on the other.

• Right after you start or change a chat, Slack or Microsoft Teams may still be adding someone. Wait a few seconds and check again
• To try again, add the person once more. Conclude then invites everyone who is missing from a channel
• If someone stays missing, Microsoft Teams won’t add them. That happens to guests and to accounts without a Teams license. Remove them from the chat, or leave them as they are

Delete a chat

DELETE /v1/chats/{chat} · scope chats:readwrite

Closes the chat and stops syncing it. Conclude archives the Slack channel and deletes the Microsoft Teams group chat. Microsoft Teams can’t archive a group chat, so the members lose its history in Microsoft Teams. The audit log records connect.chat.deleted.

On a chat with another organization, Conclude closes the channels of both organizations. Any member can do this, without the Create chats permission. The audit log records bridge.chat.closed.

curl -X DELETE https://api.conclude.io/v1/chats/Y-7f9h1j3l -H "Authorization: Bearer $ACCESS_TOKEN"

The response can have warnings, a list of messages for people to read. They name what Conclude couldn’t clean up, such as a channel it couldn’t archive.