Skip to main content

How we broke your Slack app

Hello! You are here because three monumental things changed on the Slack platform today, February 24, 2021.

What changed​

These deprecation and retirements are rolling out gradually on February 24, 2021. Your apps or integrations may work fine in one workspace but break in another. Stay tuned to our Twitter account for live updates about the retirement.

Retired Web API methods​

We retired every Web API method in the channels.*, im.*, mpim.*, and groups.* namespaces. Requests to these methods now return a method_deprecated error.

Events API event envelope changes​

In the Events API, authed_users & authed_teams are now truncated to a single entry.

  • Here's what to consider about the Events API changes.
  • The new apps.event.authorizations.list method replaces relying on authed_users and authed_teams in the Events API.
  • SDKs and tools don't use these fields by default. If you've written code that uses them directly, you'll want to investigate.
  • If your app only uses bot/app subscriptions and is only installed on one workspace, you shouldn't have anything to worry about.

Web API method authentication changes​

Newly created Slack apps and custom integrations may no longer send token as a query string parameter and must send it instead as a POST parameter or better yet, a HTTP Authorization header. Existing apps may continue doing what they already do.

  • Here's what you need to know.
  • If you create a new app or legacy custom integration-based bot (or hubot), you'll need to send token to us the preferred way.
  • If you use a rare kind of blueprint-based app, newly created apps from that blueprint must also follow this rule.
  • There is no impact to existing apps.

Need help?​

We hope this is enough information for you to help yourself should any of this have taken you by surprise.

However, if you still need our help we are ready to assist you!