---
title: "List messaging channels"
description: "Returns Telegram and Slack, whether each is available on this deployment, and the account's connection on each."
canonical: "https://www.cool.computer/docs/api-reference/messaging/list-messaging-channels"
---
# List messaging channels

> Returns Telegram and Slack, whether each is available on this deployment, and the account's connection on each.

```http
GET https://api.cool.computer/api/messaging
```

Returns Telegram and Slack, whether each is available on this deployment, and the account's connection on each. Direct messages from a connected identity, and its mentions of the Slack app in a channel, become chat turns, each answered where it was asked. A Telegram chat continues one Cool Computers chat; each Slack thread is its own. Callers: the account owner, with the browser session, a user API key or an access token; organization API keys are refused, as for starting a chat.

## Authorization

- A Cool Computers API key, user access token, or claimed agent access token in the Authorization header. Follow https://www.cool.computer/auth.md for agent registration and https://www.cool.computer/authentication.md for direct user credentials.

## Responses

- `200`: The messaging channels.
  - `application/json` (object)
    - `providers` (array of object, required)
      - `provider` ("telegram" or "slack", required)
      - `available` (boolean, required): Whether this deployment has the provider's credentials.
      - `connection` (null or object, required)
        - object
          - `display_name` (string, required): The Telegram username or Slack workspace name.
          - `connected_at` (string, date-time, required)
- `401`: Unauthorized.
- `429`: Too Many Requests. If the problem code is api_request_rate_exceeded, wait for Retry-After seconds; other problem codes describe a separate limit.
- `500`: Internal Server Error.
- `default`: A machine-readable API error with a stable code and recovery instruction.

An error is an `application/problem+json` document with a stable `code`; [API errors](/docs/api-reference/errors) says how to handle one.

## Example

```sh
curl "https://api.cool.computer/api/messaging" \
  -H "authorization: Bearer $TOKEN"
```
