> ## Documentation Index > Fetch the complete documentation index at: https://docs.agentmark.co/llms.txt > Use this file to discover all available pages before exploring further. # List Slack channels available for alert notifications > Returns every channel the Slack bot installed for this app is a member of, in the order Slack returns them. Use this to discover a `channel_id` to wire into an alert with `use_slack: true`. Returns 404 `slack_integration_not_found` when no Slack workspace has been connected to the app — surface that to the user/agent so they know to connect Slack first via the dashboard. ## OpenAPI ````yaml /openapi.yaml get /v1/alerts/slack-channels openapi: 3.0.3 info: contact: email: hello@agentmark.co url: https://docs.agentmark.co description: >- The AgentMark Gateway API lets you ingest traces, create scores, and retrieve prompt templates programmatically. Most developers should use the [AgentMark SDK](/introduction/overview) for integration. The REST API is for cases where you need direct HTTP access or are building a custom integration. Versioning: every endpoint is prefixed with `/v1/`. Breaking changes ship under a new version prefix (`/v2/`, etc.) with a 90-day-minimum deprecation window — see [API versioning & stability](/api-reference/versioning) for the full policy on what constitutes a breaking vs. additive change. title: AgentMark Gateway API version: '1.0' servers: - description: Production (AgentMark Cloud) url: https://api.agentmark.co - description: Local dev server (`npx @agentmark-ai/cli dev`) url: http://localhost:9418 security: - AppId: [] BearerAuth: [] tags: - description: Ingest, query, and export OpenTelemetry trace data. name: Traces - description: List and retrieve trace sessions. name: Sessions - description: Query individual spans across traces. name: Spans - description: Create, retrieve, list, and delete score records for spans and traces. name: Scoring - description: >- Structured-filter search across observability resources, plus the machine-readable filter schema. name: Search - description: Retrieve aggregated analytics metrics. name: Metrics - description: Retrieve the effective synced project configuration. name: Config - description: List and retrieve datasets. name: Datasets - description: List and retrieve experiment results. name: Experiments - description: List prompt files and look them up by frontmatter name. name: Prompts - description: List and retrieve individual runs within experiments. name: Runs - description: Query server feature availability. name: Capabilities - description: Retrieve prompt templates by path. name: Templates - description: Per-model LLM pricing data. Public, unauthenticated. name: Pricing - description: CRUD for annotation queues — lists, create, update, delete. name: Annotation Queues - description: >- Items enqueued for review + reviewer submissions. LLM-as-judge pipelines post through the reviews endpoint. name: Annotation Queue Items - description: >- Create, list, and revoke tenant API keys. Plaintext returned exactly once at creation. name: API Keys - description: >- List and retrieve score configuration definitions from the synced project config. name: Score Configs - description: >- Trigger and inspect managed deployments. POST returns 202; deployments run asynchronously and progress is observed via GET. name: Deployments - description: >- Per-app named environments (e.g. `dev`, `prod`). CRUD for env lifecycle; promote/rollback routes land alongside in this group as feature 054 lands the saga. name: Environments - description: >- Threshold-based monitors with Slack/webhook triggers. The agent provisioning use case is the primary design target. name: Alerts - description: >- App CRUD — the top-level tenant entity every other resource hangs off. Lets a headless agent provision an app without the dashboard. name: Apps - description: Service health checks. name: Health paths: /v1/alerts/slack-channels: get: tags: - Alerts summary: List Slack channels available for alert notifications description: >- Returns every channel the Slack bot installed for this app is a member of, in the order Slack returns them. Use this to discover a `channel_id` to wire into an alert with `use_slack: true`. Returns 404 `slack_integration_not_found` when no Slack workspace has been connected to the app — surface that to the user/agent so they know to connect Slack first via the dashboard. operationId: list-alert-slack-channels responses: '200': content: application/json: schema: properties: data: items: properties: id: type: string is_archived: type: boolean name: type: string required: - id - name - is_archived type: object type: array required: - data type: object description: List of Slack channels visible to the bot. '400': content: application/json: schema: properties: error: properties: code: type: string message: type: string required: - code - message type: object required: - error type: object description: Invalid request parameters (validation failed). '401': content: application/json: schema: properties: error: properties: code: type: string message: type: string required: - code - message type: object required: - error type: object description: Missing or invalid API key. '403': content: application/json: schema: properties: error: properties: code: type: string message: type: string required: - code - message type: object required: - error type: object description: Caller lacks 'slack_integration.read' permission. '404': content: application/json: schema: properties: error: properties: code: type: string message: type: string required: - code - message type: object required: - error type: object description: No Slack workspace connected to this app. '502': content: application/json: schema: properties: error: properties: code: type: string message: type: string required: - code - message type: object required: - error type: object description: Upstream Slack API failure. components: securitySchemes: AppId: description: Application ID for tenant scoping in: header name: X-Agentmark-App-Id type: apiKey BearerAuth: description: API key (sk_agentmark_*) scheme: bearer type: http ````