---
title: "Slack Connection Status"
method: GET
path: "/api/v1/integrations/slack/connection"
tags: ["integrations"]
---

# Slack Connection Status

`GET /api/v1/integrations/slack/connection`

## Request

- Base URL: `https://api.aws.cognee.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://api.aws.cognee.ai/api/v1/integrations/slack/connection`
- Auth: API key in header `X-Api-Key`

Connection state for the Integrations page — visible to any tenant member.

Own connection (Connect/Disconnect) and CLO-377 routing are
independent: a tenant with no Slack of its own can still receive
channels routed here from another workspace, and a tenant *with* its
own Slack can *also* receive routed channels from a different
workspace's install. ``via_routing`` is reported alongside
``connected``, never instead of it — a tenant that only receives
routed channels must still see a working "Connect" for its own,
separate workspace.

## Query parameters

- `tenant_id` string, uuid, required

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/cognee/apis/cognee-api.md) - [All operations](https://skmtc.dev/cognee/apis/cognee-api/llms.txt) - [OpenAPI document](https://skmtc.dev/cognee/apis/cognee-api/revisions/a7b6c6cb8212?raw)