Go to Slack

Scheduled changes to the Slack platform

Here are scheduled changes, deprecations, and retirements planned ahead for the Slack platform.

We tweet about most of these updates from @slackapi but we also offer this wonderfully antiquated RSS feed. Slack, the service and product, has its own changelog too.


Effective September 26, 2018

  • APIs Catch up on recent changes to presence in the RTM and Web APIs and changes to come, including the deprecation of users.list's presence parameter. Read on.

Effective September 12, 2018

  • APIs The role of @username is changing on the platform but we're making the transition as backwards-compatible as possible. Read on for important updates.

Effective August 21, 2018

  • APIs Beginning August 21, 2018 the users:read.email scope is required to retrieve the email field from user profiles while using user or workspace tokens. Consult our previous announcements on this topic from 2016 and 2017 for migration tips and some historical perspective.

Effective August 14, 2018

  • APIs We're still tidying up the character limits on the text field of posted messages and gradually lowering its maximum. On April 25th, we began truncating messages greater than 500,000 characters. As of July 12, the maximum is 100,000. We'll begin truncating messages greater than 40,000 characters in August 2018. Learn more.

Effective July 19, 2018

  • APIs File threads, a replacement for file comments, is on the way! Learn about the changes ahead, some of them may break apps relying on file comments behavior and some apps may need to request additional scopes when working with files.