---
title: "Discussion on \"Stop announcing API changes in a shared Slack channel\" | Hashnode"
description: "Discussion on \"Stop announcing API changes in a shared Slack channel\". An #api-changes channel reaches everyone and gets read by almost no one. Send each change to the teams that call the endpoint instead."
url: "https://hashnode.com/posts/stop-announcing-api-changes-in-a-shared-slack-channel/6af8b05925a7011a6b518ef0"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Stop announcing API changes in a shared Slack channel](https://graphwake.hashnode.dev/stop-announcing-api-changes-in-a-shared-slack-channel?utm_source=hashnode&utm_medium=feed)

An #api-changes channel reaches everyone and gets read by almost no one. Send each change to the teams that call the endpoint instead.

23h ago · 5 min read · graphwake.hashnode.dev  
Read the article

-   [#apis](https://hashnode.com/tag/apis)
-   [#microservices](https://hashnode.com/tag/microservices)
-   [#slack](https://hashnode.com/tag/slack)
-   [#devops](https://hashnode.com/tag/devops)

## Written by

[Graphwake](https://hashnode.com/@graphwake)

@graphwake · Vancouver, Canada

  
[View profile](https://hashnode.com/@graphwake)

Founder of Graphwake. API changes between teams.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.