The Slack developer changelog is moving! We've been working hard at building out a new docs experience at docs.slack.dev, now in beta!
We improve the Slack platform every day by releasing new features, fixing bugs, and delivering fresh documentation. The developer changelog is an account of what's happening.
We also offer this wonderfully antiquated RSS feed. Use the slash command /feed subscribe https://api.slack.com/changelog.rss to receive these updates in a Slack channel.
You can also check out these related release notes for more details about our tooling:
Slack, the service and product, has its own changelog too.
Version 3.1.0 of the developer tools for the Slack platform has sprouted!
slack app link command to work with apps that have a local manifest source.slack feedback command to display a prompt for Slack CLI feedback; now you can ask questions, submit issues, or suggest features for the Slack CLI through GitHub Issues.slack feedback --name platform-improvements command has been replaced with slack feedback --name slack-platform. You can continue to use the --name platform-improvements flag until the next major version release.slack feedback command error message to account for a missing --name <id> flag and to clarify that the name is specified as a flag. You should now see: Please provide a --name flag or remove the --no-prompt flag.Version 3.0.5 of the developer tools for the Slack platform has bloomed!
slack upgrade command inside a project directory, the output now notes whether the latest SDK versions were checkedWe want to update you about our previous announcement regarding support for classic apps. After much consideration and feedback, we have decided to push back the deprecation date to May 25, 2026.
The Slack CLI is now open source! Long a staple of workflow apps built with the Deno Slack SDK—and now with recent support for Bolt frameworks—we're proud to make the ever-growing Slack CLI part of our collection of open source tooling. We love contributions from our community, so we encourage you to explore and interact with the Github repo. Contributions, bug reports, and any feedback are all helpful; let us nurture the Slack CLI together to help make building Slack apps more pleasant for everyone. Not familiar with the Slack CLI? Visit the docs and follow the installation guide to begin your journey.
Retiring of api.slack.com: as previously announced, the Slack platform and developer tools documentation are moving: the Slack platform documentation is now in beta on docs.slack.dev, and the developer tools documentation has moved to its new home on tools.slack.dev. Our next step is to sunset the old documentation experience on api.slack.com, and we plan to do so by the end of June 2025. In the meantime, you may want to update any bookmarks you have pointing to api.slack.com—but not to worry, we'll have redirects in place to make sure you end up right where you need to be!
Version 3.0.2 of the developer tools for the Slack platform is here!
slack version command to include additional descriptive information and examples when using the --help flag.slack feedback command to point to the home of our new and improved documentation on docs.slack.dev!Slack CLI version 3.0.1 delivers a handful of small improvements thank to our developer community feedback.
--token flag and it'll work when combined with the --app and --team flags.--app flag to use the specified app and it'll work when combined with the --team flag.We want to update you about our previous announcement regarding support for the files.upload API method. After much consideration and feedback, we have decided to push back the deprecation date to November 12, 2025.
Today is the day! As previously mentioned, the Slack platform and developer tools documentation are moving: the shiny new Slack platform documentation is now in beta on docs.slack.dev, and the developer tools documentation has fully moved to its new home on tools.slack.dev. The doors are open for our housewarming party 🥳 so come on in, take a look around, and let us know what you think. Thanks for coming along on this journey with us!
Version 3.0.0 of the developer tools for the Slack automations platform is here, with lots of goodies for you!
slack.json file to .slack/hooks.json, and continue to support slack.json for existing projects. There is now a warning shown in --verbose output to encourage projects to migrate their slack.json to .slack/hooks.json.invalid_app_directory error from any commands run in nested project directories, and now search for the required slack.json file in the project's configuration. We also now also check for this file at .slack/hooks.json.slack create and slack samples, to be sub-commands of the slack project command (they remain aliased as top-level commands though, so there is no change to the user experience).slack doctor command to display the manifest.source value, which will be either local or remote.slack create command with a new create journey that allows you to choose between different types of apps for Bolt for JavaScript, Bolt for Python, and Deno.slack init command, which will initialize an existing Bolt for JavaScript, Bolt for Python, or Deno project with Slack CLI support.--no-color flag.slack collaborators and slack manifest commands.slack run command encountered an error; we now exit the slack run command if this happens.We previously mentioned that we had deprecated the deno command and removed its listing from the help command. We have now removed the deno command completely. Developers who were depending on this command should now use the deno executable directly.
We've also removed support for the deprecated, pre-release Deno Slack SDK versions that used slack.yaml and project.ts files. The Run-on-Slack platform no longer supports the slack.yaml file format, and no production projects should be affected. The project.ts file was deprecated by the Deno Slack SDK in favor of manifest.ts and manifest.json files.
Version 2.33.0 of the developer tools for the Slack automations platform will be your valentine!
slack manifest command is run.slack.A new Block Kit block is now available for use! The markdown block accepts standard markdown and outputs formatted Slack markdown; intended for use in AI apps.
The Data Access API is here! This API is now available in a limited release for interested partners. Use the Data Access API within AI apps to access all the relevant Slack data you need to ensure a pleasant user experience for AI apps.
Version 2.32.2 of the developer tools for the Slack automations platform is here!
slack collaborator remove command. For more information, refer to remove collaborators and security considerations.stderr warning messages will appear properly in the console.Version 2.32.1 of the developer tools for the Slack automations platform has arrived!
1.3.2 release, we've improved the bundling used for the slack deploy command to address some issued encountered with npm imports.--force flag is used.Version 2.32.0 of the developer tools for the Slack automations platform is here!
slack env commands. We also added error messaging to these commands when the app being referenced is not a workflow app.slack env remove command now exits without erroring when there are no environment variables to remove.slack datastore commands.slack external-auth subcommands with non-workflow apps.source errors that may have caused confusion; they have been replaced with more helpful messaging.We want to let you know about some updates to our Slack App Developer Policy. Check out this changelog article to learn more.
We want to let you know about some exciting news — the Slack API and tools documentation will be moving! Check out this changelog article to learn more.
Version 2.31.0 of the developer tools for the Slack automations platform has landed! We fixed a bug that would display errors when the slack run command was interrupted during app selection. The fix also includes an org_grant_exists error, which is raised if an attempt is made to grant installation permission to another workspace when your app has already been granted one.
We want to update you about our previous announcement regarding support for legacy custom bots and classic apps. After much consideration and feedback, we have decided to push back the deprecation date for classic apps by 6 months: we will now discontinue support for them on March 31, 2026. Nothing will change for legacy custom bots, of which the original deprecation date was March 31, 2025.
Boo! Version 2.30.1 of the developer tools for the Slack automations platform has sneaked up behind you. We fixed a bug such that expired tokens will now be removed from your local credentials, and the token_expired error will be logged when debugging if returned when using the slack logout command. No tricks, only treats!
Version 2.30.0 of the developer tools for the Slack automations platform has spookily appeared!
slack deploy now respects use of the --force flag. We also fixed a few other bugs related to app manifest validation to make things run more smoothly.slack create command will use either the absolute or relative path provided when creating your app.We want to let you know about some upcoming changes to support for legacy custom bots and classic apps on the Slack platform.
We're excited to announce that the following new features have launched!
Version 2.29.2 of the developer tools for the Slack automations platform is hot off the press!
slack login command, the Slack CLI will now suggest also running the slack app list command. When logging in outside of a project directory, the Slack CLI will continue to suggest running the slack create command to create a new project.Custom workflow steps for all Slack apps are available today! Refer to workflow steps and custom steps for Bolt apps for more details.
Version 2.29.1 of the developer tools for the Slack automations platform has arrived!
pwsh to powershell for better backwards compatibility.--source flag with the manifest info command. The flag can be set to either project or remote.npm install command.--workspace flag recommendation with a --team flag recommendation.In the Deno Slack API 2.8.0 release, we've added an event_timestamp property to all event trigger data objects. Refer to the event response object for more details.
Version 2.26.0 of the developer tools for the Slack automations platform is here!
datastore count Slack CLI command by adding a default for an empty query expression if one isn't provided.In the Deno Slack SDK 2.12.0 release, we've added the add_bookmark Slack function and the team_id type. In addition, you can now pass the optional team_id parameter to the create_channel and create_usergroup Slack functions.
Version 2.25.0 of the developer tools for the Slack automations platform is kicking off the summer fun!
apps.json file with app IDs for your existing apps using the slack app link command. Refer to app commands for more details.slack collaborator add, slack collaborator list, and slack collaborator remove commands.slack create command. We also now suggest installing project dependencies if an error occurs when running this command.slack manifest validate command.Version 2.24.0 of the developer tools for the Slack automations platform has landed!
function distribute command to function access (however, the distribute subcommand has been added as an alias so you can still use function distribute). Refer to custom function access for more details.As of May 16, 2024, newly-created Slack apps are no longer able to access the files.upload API method. Learn how to use our new asynchronous upload flow to migrate your existing apps and integrations by March 11, 2025.
In the Deno Slack SDK 2.11.0 release, we've added a new Share Canvas in Thread Slack function.
The September 2024 retirement of Steps from Apps for our legacy Workflow Builder approaches quickly. Learn more about what this means for your steps and workflows in this changelog article and survival guide.
Version 2.23.0 of the developer tools for the Slack automations platform is here!
SLACK_API_URL environment variable to the preferred API host used in the auth process.slack doctor command.We updated our developer policy to clarify guidance around circumventing Slack limitations. We also tweaked our developer program agreement. Here is the short list of changes.
Coded event trigger improvements are live! You can now set an event as all_resources: true instead of listing individual channel_ids. This allows your event trigger to listen to any channel your app is part of. Check out scoping channel-based event triggers for more details.
Version 2.22.0 of the developer tools for the Slack automations platform is here!
team_access_not_granted error when redeploying an app.outgoing_domains attribute within an app's manifest.slack create.In the Deno Slack SDK 2.10.0 and Deno Slack API 2.4.0 releases, we added support for the all_resources event for event triggers. Refer to scoping channel-based event triggers for more details.
Our Web API method files.upload is now deprecated and will retire on March 11, 2025. Learn how to use our new asynchronous upload flow and migrate your apps and integrations.
Version 2.21.0 of the developer tools for the Slack automations platform has sprung!
doctor hook. To enjoy the improved slack doctor command experience, existing Deno Slack SDK-based apps must have their deno-slack-hooks dependency upgraded to the latest version (v1.3.0).get-manifest hook when attempting to get a manifest rather than checking for a slack.yaml file, we now surface any errors that are returned when getting the manifest.In the Deno Slack SDK v2.9.0 release, the invite_user_to_channel built-in function makes the user_ids parameter optional rather than required. In addition, a usergroup_ids parameter was added, allowing you to invite entire user groups.
As of June 4, 2024, you can no longer create new classic apps or legacy custom integration bot users. Learn how this may impact you and your team.
Versions 2.20.0 and 2.20.1 of the developer tools for the Slack automations platform have landed!
$ slack datastore get '{"datastore": "todos", "id": "42"}'$ slack datastore get --datastore tasks '{"id": "42"}'not_authed error that explains how to log in and authorize the Slack CLI.Version 2.19.0 of the developer tools for the Slack automations platform has joined the stage!
GetHooks errors display properly.The Deno Slack SDK v2.7.0 release brings new Slack functions for Canvases! Refer to the Canvas section of the Slack functions catalog for more details.
Version 2.18.0 of the developer tools for the Slack automations platform has joined the party!
v6.0. If you attempt to use an older version of PowerShell, you may encounter errors reading the Slack Configuration file (slack.json) or running the get hooks hook.put and bulkPut, Retrieve items with get and bulkGet, and Delete items with delete and bulkDelete, respectively.slack create command with the --force flag.trust_unknown_sources property in your config.json file.slack deploy.Version 2.17.1 of the developer tools for the Slack automations platform is hot off the press!
SLACK_APP_TOKEN and SLACK_BOT_TOKEN environment variables when you run your app.@slack/cli-hooks is installed.slack create command.File upload functionality is now available in Block Kit! Use the new Block Kit file_input element in your apps or functions. Get more details here.
Securely render your internal images in modals and messages. You can now use Slack file objects to reference Slack-hosted image files within image blocks and image block elements.
Version 2.15.0 of the developer tools for the Slack automations platform is home for the holidays!
deno command and removed its listing from the help command. The deno command is slated to be removed completely in an upcoming release.api.slack.com are no longer blocked by a permission error for local apps.(local) tag to the display name of local apps.Version 2.14.0 of the developer tools for the Slack automations platform is here!
SLACK_CONFIG_DIR environment variable to the --config-dir global flag.uninstall command is now available from the list displayed when using the --help flag.Version 2.13.0 of the developer tools for the Slack automations platform has landed!
--all-org-workspace-grants flag to the app list command so you can display all grants instead of only the first three.workspace and org language into team; as such, we have added a --team flag and deprecated the --workspace flag. Note that this will not affect the usage of workspace or org when it is necessary to distinguish between them; for example, with the hermes auth list and trigger access commands.delete command when running the uninstall command, so you may now only uninstall an app rather than deleting the app entirely along with all of its data.deno-reverse-string sample app references to use deno-started-template instead.usr/local/bin directory if it is missing when installing the Slack CLI.--trigger-def flag.Keep your user data secret and safe. Both versions of the SCIM API now support restricting token usage by IP address.
Hot on the heels of last week's release, version 2.12.0 of the developer tools for the Slack automations platform is here!
npm: specifier when importing modules for both locally run and deployed apps. For more details about using npm: and node: specifiers, refer to Node.js APIs and npm packages.slack app list command to display Enterprise grants for multiple workspaces.Version 2.11.0 of the developer tools for the Slack automations platform has spookily appeared!
manifest, deploy, install, triggers create, and triggers run) to catch errors if a connector is not installed, attempt to install any certified apps related to connectors mentioned in the manifest, and then re-validate the manifest.--file flag to the function distribute command (renamed to function access) so that you can manage access and distributions with a configuration file instead of multiple commands.Version 2.10.0 of the developer tools for the Slack automations platform has entered the chat! We've updated the deploy command to prompt you to select an organization workspace, similar to the run command. We also added a little more polish to the Admin-Approved Apps flow, added support for the apps.certified.install method (coming soon to an API near you!), and implemented a few bug fixes behind the scenes to keep things running smoothly.
Ever wanted to include the formatting available in the message composer to your form modals or Block Kit surfaces? You can now use the rich text input to collect formatted answers from users and also post Block Kit payloads that include rich text blocks. Try them out in Block Kit Builder now. Hint: Check-out the "edit" functionality (hover and click the pencil icon) to compose rich text blocks in-line.
Version 2.9.1 of the developer tools for the Slack automations platform is here! We now order functions by callback ID for easier sorting when you call the function distribute command (renamed to function access). We've also formatted and streamlined the install script and some of our error descriptions for a smoother, more pleasant experience.
Starting September 19, 2023 the Slack API's minimum required CLI version is changing from v1.18.0 to v2.9.0 for Enterprise Grid (for non-Enterprise Grid, the minimum required version is v1.18.0). If you attempt to log in with an older version, you'll receive a cli_update_required error from the Slack API. Run slack upgrade to get the latest version. Refer to the quickstart guide for more details.
Version 2.9.0 of the developer tools for the Slack automations platform has landed!
deploy and install your app by using the --org-workspace-grant flag.--info flag for a more streamlined experience.--app and an active token via --token flags.New Admin API methods are now available! Use these methods to manage the same workflow permissions and approval requests you can from the admin settings site dashboard, sans the UI and with bulk operations.
Version 2.8.0 of the developer tools for the Slack automations platform has arrived!
app list command no longer requires authentication, and will instead display an unknown app status in cases where no authentication is found.run, deploy, and delete commands will now resolve organization-level authentication in cases where workspace-level authentication is missing.We're retiring support for traditional Slack apps providing Steps from Apps to our legacy workflow builder and workflows created with it. Read on to learn whether your apps or workflows are impacted.
New submissions to the Slack Marketplace are now required to have a minimum of 10 active workspace installations in order to be reviewed. Read more in our submission guidelines.
Version 2.7.0 of the developer tools for the Slack automations platform has arrived!
slack trigger list --type=<string> flag to only list triggers of a specific type: For example, slack trigger list --type=shortcut. We've also supported flag values for --type=<string> are all, shortcut, event, webhook, scheduled, and external.--help to any command. For example, slack external-auth add-secret --provider github --secret my-secret-value. slack app list command to improve displaying apps you are not authenticated to access. For example, local apps now display a (local) label and install status is now shown as Status: Unknown.workflow, function, datastore, customType, event or provider. This helps prevent unexpected behavior at runtime.Version 2.6.0 of the developer tools for the Slack automations platform has arrived!
.github directory will no longer be included in new projects created from one of our sample apps.feedback@slack.com—email us for assistance if your app returns an internal error code.slack app list command now returns Status: Installed instead of Status: Unknown for an installed app.slack run or slack deploy in a non-interactive environment, regardless of how many triggers might exist.slack run session.type field of functions and datastores were made in the Deno SDK.We introduced breaking changes to APIs and events related to saved items and reminders. Learn more about the impact to your apps.
Version 2.5.0 of the developer tools for the Slack automations platform is hot off the press!
slack app delete command.--hide-triggers flag to the slack run and slack deploy commands to prevent retrieving and displaying application triggers.trigger list --limit <n> command.named_entities. The include-app-collaborators flag will allow you to skip this prompt.slack activity command to support datastore event and error logs. For more information, refer to logging.--token flag is set, background checks for updates will now be automatically disabled.curl install of deno if deno upgrade should fail.slack logout command now accepts the --workspace flag.--show-triggers flag from the slack run command, as the command now displays all of your app's triggers and their types.Beginning June 28, 2023, version v1.17.0 and below of the Slack CLI is deprecated. We recommend reinstalling the Slack CLI to get the latest version. Learn more.
Version 2.4.0 of the developer tools for the Slack automations platform is now available!
-v.-d flag to bypass Deno installation in the Linux/macOS installation script.1.31.1.workspace command with a new app command.config-dir global flag visible.auth flag in favor of token.app list command to display installation status.Version 2.3.0 of the developer tools for the Slack automations platform has arrived!
external-auth remove command now allows you to select a token for deletion.external-auth select-auth command allows you to select a unique auth for each of the workflows in an app. This command is mandatory when using new coded workflows that have a step containing credentialSource DEVELOPER; that is, every time a coded workflow is created, this command must be called after the external-auth add command.slack auth token and slack auth revoke commands allow you to manage service tokens.slack auth token command allows you to get the slackauthticket and copy and paste it into your workspace to exchange for the service token. The service token will not be saved to your credentials.json file; instead, it is presented in the prompt for you to copy and paste to your CI/CD pipelines. Once you obtained a service token, you can use the slack login --auth <your-service-token> command to authorize your Slack CLI. The service token will not conflict with your regular authentication token; you can continue using your regular authentication token within the Slack CLI while using the service token for your CI/CD pipelines.--token <token> flag allows you to pass the service token used by requests requiring authentication. For example, to install an app, use: slack install --token <your-service-token>. To create a trigger, use: slack trigger create --token <your-service-token> --app deployed --trigger-def triggers/trigger_def_file.ts. To deploy an app, use: slack deploy --token <your-service-token>--experiment [name,name,...] flag.Version 2.2.0 of the developer tools for our beta Slack platform has landed!
trigger info command now also shows who has permissions to run the trigger.--no-color flag, which removes all ANSI sequences for color as well as emojis, giving you plain text output from the Slack CLI that's perfect for piping to a text file.datastore query command now supports a cursor argument to help you paginate your results the way you want.Today we're announcing that the Slack automations platform—which provides a faster, more flexible way to build automations on top of Slack–is generally available to developers. The platform's overhauled architecture gives developers more ways to build, code, and ship custom apps and workflows more quickly and easily in an environment that's both secure and compliant. Read the announcement or follow the Quickstart to get started today.
We released v1.20.0 of the developer tools for our Slack platform beta. Changes include a number of user-requested improvements to the Slack CLI and details about an upcoming maintenance window next month, and breaking changes landing the month after that, which may require you to update your apps.
We released version v1.18.0 of the developer tools for our Slack platform beta. View our new curated collection of sample apps for inspiration and illustration.
Three new endpoints for admins to manage role assignments are now available: admin.roles.listAssignments, admin.roles.addAssignments, and admin.roles.removeAssignments. Explore other useful methods for managing your users and workspaces here.
A bevy of new Block Kit input elements await developers soliciting input from users including the often requested combined date and time picker. Collect links with the URL input element or email addresses, numbers, too.
We released version v1.14.0 of the developer tools for our Slack platform beta. Update your tools here.
We updated the fine print and added default placeholder text for the following Block Kit elements: channels_select, conversations_select, multi_channels_select, multi_users_select, and users_select.
At last, member_joined_channel now works as you'd expect for multi-party direct messages (MPIM). Be sure to add the mpim:read scope to receive these events!
We're cleaning up some lingering behavior in our legacy Real Time Messaging API. In message events streamed over the RTM API, channel and usergroup mentions will no longer include entity names. Still need entity names? Access them using Web API methods such as conversation.info and usergroups.list. Alternatively, consider using the Events API, which also supports WebSockets, to receive message events.
Today we permanently alter the behavior of the retired Web API method rtm.start: those still using this method will receive the more reliable but brief response of the rtm.connect method. We expect some apps to break but we are here to help! Read the full announcement here.
To better accommodate customers at Dreamforce next week, we've moved rtm.start's final retirement date to September 27th, 2022. Learn more about the future of rtm.start and how it may impact your app.
Several new tools for app developers are now available as part of our Slack platform open beta. Developers can ship higher-quality apps and workflows quickly with a streamlined development lifecycle, including secure hosting and data storage in Slack.
Keep track of who gets added to DM conversations. You can now monitor the dm_user_added audit event with the Audit Logs API.
On September 13th, 2022, we will provide a preview of the rtm.start future behavior. If you still use rtm.start to connect to Slack, learn more about when this preview will be happening in your time zone and how it may impact your app.
Slack is used by public sector teams and their partners for being faster, better organized, and more secure than email. If you're a government agency, contractor, or just intrigued by how Slack supports government communication, our GovSlack documentation is the place to be!
Bring users information and delight in your Slack apps with the video block now available in Block Kit. Read on to learn more on how to embed videos in your app.
Be informed about specific changes to users' data. One of three events will now be dispatched alongside the user_change event: user_huddle_changed, user_profile_changed, or user_status_changed.
The file may be deleted, but the record of the event won't be. You can now monitor file_deleted audit events with the Audit Logs API.
Messages are how people communicate in Slack, message metadata is how apps communicate with apps! Read on to learn about how to spark more automation with your app throughout Slack.
Help users find links, messages, and files germane to a channel's distinctive purpose with the Bookmarks API.
The admin.users.unsupportedVersions.export API allows you to export users using unsupported software within your workspace. Read on to learn more.
Block Kit button elements can now utilize the optional accessibility_label field, which allows you to write longer descriptive text for a button. Learn more.
The admin.apps.requests.cancel method allows admins to cancel app approval requests within a workspace or Enterprise Grid. Learn more.
If you still use rtm.connect or rtm.start to connect to Slack, you'll notice that all WebSocket URLs now begin with wss://wss-primary.slack.com.
As previously announced, apps & integrations created after today, November 30, 2021, must use rtm.connect instead of the deprecated rtm.start when connecting to the RTM API. Learn more about this and what's next for existing users of rtm.start.
Block elements can now utilize the focus_on_load field within Block kit messages, which allows you to pick one specific Block element to auto focus on. Learn more.
The default Slack Connect invitation type when using conversations.inviteShared has changed. Invites are now sent to limit the recipient's actions to only sending messages. The new external_limited argument can be used to control which invitation type is sent.
We're starting to roll out a new, opt-in beta UI that lets you configure and reconfigure apps using manifests. We're also launching new App Manifest APIs to let you create and manage all your apps programmatically. Learn more.
One of our earliest API methods is taking a well-deserved retirement on September 27, 2022. For existing apps, rtm.start will instead return an equivalent response to rtm.connect. Beginning November 30, 2021, newly created apps and integrations will only be able to use rtm.connect. Learn more.
Introducing two API methods that return information about workspaces previously only available in rtm.start: team.billing.info and team.preferences.list.
Slack Developer Tools now offers the Platform Guide, an interactive and introductory education experience for developers interested in learning the basics of building a Slack app within a Slack app.
Pick a time, any time. The timepicker block element is released out of beta and available to use in your spiffy apps. Click here to add the timepicker to your timeless Block Kit messages.
The link_shared event is changing, bringing unfurls—allowing users to see what's in a link—into the message composer. Read more on magic unfurls for uninstalled apps in the message composer.
In the app approval APIs, you may now distinguish the apps built within your organization from those developed externally—or by Slack—with the developer_type field.
Legacy workspace apps are now completely retired. They won't function anymore and eventually will be completely removed from our databases. If you run into trouble, please reach out.
The link_shared event is changing to bring a little more magic to app unfurls. Read up on the changes, which roll out to free teams on September 1, 2021 here.
Modern Sign in with Slack uses the OpenID Connect protocol to make signing in with Slack faster and more flexible. Try it today.
You can now manage Slack Connect directly for your organization using an app. Read up on the Slack Connect APIs.
Use manifests to create and manage apps from saveable, shareable, and relatable YAML and JSON. Try out some sample manifests in our new guided tutorials.
Apps using classic message attachments have an updated look. Attachment images now have a hover menu and will mostly appear to the right of text. Click here to review the new design. Consider using Block Kit to have more control over how images render.
We're teaching old blocks new tricks. Starting April 20, 2021 input blocks are now able to exist within messages, allowing you to gather information more swiftly within conversation. Learn more about how to extend your Block kit messages.
Apps may now broadcast messages to users via direct message without handling unnecessary or unsupported conversation and slash commands. Starting March 29, 2021, this feature will be default for all newly-created Slack apps. Get started by visiting the App Home tab of your existing Slack apps.
Newly created private channel IDs now always begin with the letter C, just like public channel IDs already do. The Conversations API will tell you whether a conversation is private or not with the is_private boolean field.
Legacy workspace apps, deprecated since October 2018, will officially retire on August 24, 2021. Learn if and how this may impact your apps.
The admin.analytics.getFile method now returns daily data about conversations in public channels. Members analytics remain available. Explore what's happening on your Enterprise Grid workspaces.
Three deprecations take effect today, February 24,2021. First, new apps may no longer pass tokens as query parameters. Second, Conversations API methods are now required over their typed counterparts: channel.*, group.*, im.*, and mpim.*. Third, event payloads no longer contain full lists of authed_users or authed_teams—instead, use a new method to learn the full list of authorizations an event is visible to. We know keeping up with best practices for Slack apps is a lot to handle—thank you for allowing us to make the platform better. Keep reading.
If your app makes use of user emails, be on the lookout for relay email addresses. When users sign into Slack via Apple, their emails may appear as anonymized relay addresses. Relatedly, Sign in with Slack won't work with these users.
Now you can decorate your ephemeral messages requesting authorization with Block Kit using chat.unfurl. Learn more about our continued improvements to message unfurling.
When a user initiates a private channel share via Slack Connect, the channel's ID changes. Subscribe to channel_id_changed to learn the new IDs for the private channels visible to your app.
Your app can now count its workflow steps with the help of four new events: workflow_published, workflow_unpublished, workflow_deleted, and workflow_step_deleted. Use these events to stay informed on workflows—from unpublished to published and back again—that make use of steps powered by your app.
Socket Mode supplies your app with events and interactive feature payloads over a dynamic WebSocket URL. Read more on the new way to skip static, public HTTP endpoints—now supported by all SDKs.
Submissions to the Slack Marketplace now require Security & Compliance information. Read more in our submission guidelines.
Reach a whole new world of workspaces: build an app that can be deployed across an entire Enterprise org.
Apps created after February 24, 2021 will no longer be able to send token as a query parameter. All existing apps require no changes. Learn more.
The admin.analytics.getFile method returns compressed JSON files with workspace member analytics for the day of your choice—now available for Enterprise.
App modals can now be 'popped out' by users, giving them their own resizable, movable window. No app changes are needed, we just wanted to pop in with an update.
Block Kit checkboxes and radio buttons are now available to use in messages. Quickly and conversationally collect information from users by including them inline.
Gather data from users directly from your App Home—input blocks can now be added to Home tabs. Additionally, input blocks can now dispatch block_actions payloads when someone interacts with them. Read about the new dispatch_actions flag.
We refreshed the look of your app's listing in the Slack Marketplace. Among the changes: a Features tab shows your app's entry points—like shortcuts and slash commands.
We updated our developer policy and API terms of service to clarify language around export controls and international data transfers. Here are the changes.
Alongside upcoming changes to the Events API, you'll find numerous new features: a new authorizations field delivered with events, a new method for listing installations, a new scope—even a new token type for working across an entire organization.
Starting February 24, 2021, event payloads will no longer contain full lists of authed_users or authed_teams. Instead, you can call a separate method if you need a full list of parties an event is visible to. Read up on the upcoming changes here.
On September 29, 2020, view_submission and block_actions payloads will begin including full state for messages, modal, and App Home views. Learn more.
On September 15, 2020, you'll no longer need to worry about different global and local IDs for Enterprise users. Users will have a single, global ID across an Enterprise org, which may begin with either U or W. Read more.
In responses from the search.messages method, four fields—next, next_2, previous, and previous_2—that sometimes appeared are now deprecated and will no longer appear in responses, beginning December 3, 2020. Let us know of your questions or concerns.
Get a handle on creating channels, setting preferences, and connecting new workspaces—all with a single app. Use the APIs for channel management, available to Enterprise Grid organizations.
We slightly changed your App Home's appearance by refreshing the default text style and how hint text is displayed. We hope you'll enjoy it.
Users may now mute and unmute their conversations with apps like they can with other channel types. When a user mutes a conversation with your app, the messages you send are still delivered and a colorful badge will continue to surface in their channel list. However, users will not receive a direct operating system or browser notification on delivery.
Slash command invocations will now include an api_app_id parameter with your Slack app's ID. This parameter will better assist you in handling commands from multiple applications or environments.
New header blocks let you provide stronger delineation between groups of content in your app surfaces. Stay ahead of the game by learning how they work.
Expand Workflow Builder's capabilities by creating reusable, custom steps that any builder can add to their workflows. Workflow Steps from Apps is now in open beta. What’s your app’s next step?
Previously, when a user mentioned an app that wasn't party to the conversation, the user could Invite the app to the conversation, Let Them Know, or Do Nothing. The Let Them Know button didn't work. We've fixed that mistake by removing the button, and updated our documentation on the app_mention event as well.
Mark messages unread for users with conversations.mark. Bespoke clients and personal utilities should use this method sparingly.
The URL where users manage existing installations of Slack apps is changing to https://app.slack.com/apps-manage/. You might not even notice the difference, but we’re letting you know just in case.
With Slack Connect, channels connect multiple workspaces and organizations with ease. Here's an overview of how to develop apps for channels between organizations.
A change to user_change events: we've fixed a bug where these events dispatched to subscriptions from all workspaces in externally-shared channels. Now, user_change events are dispatched only to the home workspace of an externally-shared channel.
If you create a new Slack app and use deprecated methods like channels.*, im.*, mpim.*, or groups.*, you'll now receive a method_deprecated error. Existing apps will receive warnings but still have until February 24th, 2021 to migrate to the Conversations API. Learn more.
Maintain a membership allowlist for private channels using admin.conversations.restrictAccess.addGroup, admin.conversations.restrictAccess.removeGroup, & admin.conversations.restrictAccess.listGroups methods, now available for Enterprise organizations. Update: These methods were renamed but the old names will continue to work.
We recently updated Block Kit Builder with additional preview options and more convenient ways to copy, paste, and dispatch payloads. There's more beauty to it too.
The deadline for all Slack apps to use the Conversations API—instead of its antecedents—has moved from this November to February 24th, 2021. Newly created Slack apps won't be able to use channels.*, im.*, mpim.*, or groups.* methods beginning June 10th, 2020. Warnings will soon be included as part of deprecated responses. Learn more.
Legacy tester tokens may no longer be created. Existing tokens may continue to be used, regenerated, or revoked. Tokens left unused for three months or more will be regularly revoked. Learn more from our previous announcement.
Complete your IDP groups with custom default channels, courtesy of the admin.usergroups.* API methods.
Starting July 1st, 2020, rate limits will apply to all SCIM methods. Please make sure any apps using the SCIM APIs remain within these limits and humbly handle HTTP 429 responses.
A more direct route to messaging in response to modals: the new default_to_current_conversation field allows your conversation_select and multi_conversation_select menus to be pre-populate the currently open conversation.
The shortcuts button is now available for all Slack workspaces, so we're taking global shortcuts out of beta.
Previously, OAuth Redirect URLs could contain anchors (#). We've fixed that mistake, and anchors are no longer allowed.
Beginning June 10th, 2020, all newly created Slack apps will be unable to use the deprecated methods in channels.*, im.*, mpim.*, and groups.*. Existing apps have until February 24th, 2021 to migrate to the Conversations API. Learn more.
Visually highlight destructive actions by using the new style parameter in confirmation objects.
Give app installers good reason to trust your app: submit security and compliance information to the Slack Marketplace today.
Tune out the noise—you can now use filters with conversation lists in select and multi-select menus. Learn more and start filtering.
Give users clear entry points to your Slack app with Shortcuts. App Actions are now called message shortcuts. They're joined by new global shortcuts that allow users to initiate interactivity from anywhere in Slack. Learn more here.
We didn't turn off the replies array field found in threaded parent messages on October 18th, 2019 like we said we would. The new date is March 31st, 2020. Please use the reply_users, reply_users_count, and latest_reply fields instead.
New guidelines for Slack Marketplace submissions have arrived to help ready your app for the world.
Using two new scopes, your Slack app can adjust its message authorship and post in any public channel.
The creation of legacy test tokens is now deprecated and will permanently retire on May 5th, 2020. Learn more about using Slack apps to build firmly scoped integrations.
Starting February 18, 2020, unexpected results using the SCIM API when rapidly updating data on the same user or group will become a thing of the past.
It's a win for webhooks: you can skip the small stuff and trigger a workflow with a web request.
Check another item off your Block Kit wishlist - we've added a checkbox group element to modals and Home tabs for your multiple choice input needs.
You can submit information to the Slack Marketplace on your app's privacy policy, data retention, security tests, and compliance with major laws. Read our blog post on the new Security & Compliance feature, now in open beta.
Slack apps, with subtler permissions and more intuitive behavior, are now the default when you create an app. Get started by building or migrating.
Your app's new Home tab is out of beta. Design a comfortable place for users to get work done using Block Kit Builder and publish them for users using views.publish. Get started by diving into the Home tab docs.
Give users a key to directly open your Home tab. Read our updated deep-linking guide to see how you can create links to specific tabs in your App Home.
We are deprecating all channels.*, groups.*, im.*, and mpim.* Web API methods in favor of their Conversations API replacements. Migrate to conversations.* as soon as possible, as these deprecated methods will retire on February 24, 2021. Read on.
We didn't set out to produce almost 700 pages of documentation but you can search it all now on api.slack.com/search.
Slack apps may now be submitted to the Slack Marketplace. Check out our guide to migrating your existing app to use granular permissions.
Your App home is going mobile — you can now interact with an app's Home tab from iOS and Android clients. We recently published a new App home tutorial to help you build, or you can read the Home tab docs.
Help users make informed decisions when considering your app by listing the languages it's fluent in and any pricing model that applies to it. You can provide this info as part of the Slack Marketplace submission process.
We're removing the misleading and undocumented guest_channels field from user profile objects belonging to guest users. The users.conversations method is an accurate way to query the channels a guest user belongs to.
Slack has but one REST API, the SCIM API, and it's now fully standards-compliant with SCIM 1.1 when using the HTTP PATCH method to update user records.
Your apps have always needed a better home, right in Slack. Now apps with bot users can use Block Kit with a new surface called the Home tab. Learn how to use this new space to provide users with a persistent place for dynamic experiences.
Radio is alive and well in Block Kit. Obtain a singular choice from users using our new radio button elements.
Craft a workspace faster than a cup of coffee and fill it with users, admins, and owners. Check out the APIs for creating workspaces and managing users, now available for Enterprise Grid organizations.
Slack apps can act independently of a user token. Build a bot user powered by only the specific permissions it needs. Check out our open beta for newly created Slack apps.
Announcing new pastures for Block Kit beyond messaging: trigger dynamic modal interfaces to provide linked user experiences invoked from messages, actions, or slash commands.
Embrace procrastination — allow users choose from multiple options in interactive workflows. Use new multi-select menus in all your Block Kit surfaces.
This autumn or soon thereafter, users will begin editing messages using a WYSIWYG (what you see is what you get) interface. When they do, their posted messages will appear slightly different throughout our APIs. Learn more.
Two new events, channel_shared and channel_unshared, now notify your app when a channel is shared or unshared.
A single admin app can now approve or restrict other app installs across an entire Enterprise Grid org. Get a little meta, and a lot more time-efficient, with the APIs for app management.
As previously announced, pins.add will stop accepting file and file comment IDs beginning August 22, 2019. Similarly, reactions.add will no longer allow file and file comment parameters. Nowadays, apps and users pin & react to messages about files instead.
On March 4, 2020, we'll require all apps, custom integrations, bots, and users communicating with Slack to use TLS version 1.2 or higher. There will be a 24 hour test deprecation on February 19th, 2020. Read more details on why and how to upgrade.
Enterprise Grid admins may now use the admin.users.session.reset method to wipe a user session, logging out a user whose device may have been stolen or compromised. Learn more about the new method, as well as the new scope required to use it.
Your app may now encounter channels shared between workspaces on Enterprise Grid. As a result, it's even more important to use the Conversations API methods to safely handle channels both shared and unshared.
Using the SCIM API's GET /Users or /Groups methods? Their count parameters will no longer accept values above 1000 beginning August 30, 2019. Learn how to prepare.
As announced previously, the dnd.teamInfo method now requires the users parameter. An explicit list of users helps you, and us, avoid slow API calls.
As previously announced, the files.comments.add and files.comments.edit methods are retiring today. Also, files may no longer be pinned to channels. The pins.add method will no longer accept files or file comments beginning August 22, 2019.
Better built-ins. Nifty type hints. Easier RTM event handling. Build for the future with the new Python SDK V2.0.0, lovingly crafted with Python 3.
Parent messages in a thread will no longer explicitly list their replies. Instead of a large replies array containing threaded message replies, we'll provide a lighter-weight list of reply_users, plus a reply_users_count and the latest_reply message. These new fields are already available. We'll remove the replies array on March 31st, 2020. Read up on threaded messages here.
Make your app a better listener with the app_home_opened event. When a user enters a conversation with your app, you can trigger a friendly onboarding flow, a whimsical welcome message, or a deep-dive into dialog. Read more.
Retrieve all active incidents, rather than just the most recent one, using version 2.0.0 of the Slack Status API. Read more.
Buttons in message blocks have gained some color. Use the new style field to visually compel and alert users.
We're returning a more descriptive limit_required error when you call users.list or channels.list for teams containing tens of thousands of responses. To avoid the peril of errors entirely, use pagination.
Taking a novel approach to pagination, the v5 release of our Slack SDK for Node.js supports Node v8 LTS and above. It also splits the client into three separately installable packages optimized for speed and bundle size. Work with other languages or frameworks? Browse other tools built for you.
When querying dnd.teamInfo, the users argument is required beginning June 3, 2019. Future-proof your app by explicitly listing which users you wish to see Do Not Disturb settings for.
Harness a hint of time travel for your app. Schedule messages for delivery at the time of your choosing.
We're starting to enforce (more firmly) the 5GB file upload limit for workspaces on a Free plan. Some API endpoints will yield tombstoned files with the content redacted. Read more.
We're retiring the files.comments.add and files.comments.edit methods on May 22nd, 2019. Learn more.
We're loosening up limits on dialogs. You can use five extra elements (ten total) and lovingly label them with longer lengths of letters.
When your exacting maths require the precise number of members party to a particular conversation, use the new include_num_members parameter with conversations.info.
Build better messages with Block Kit, a set of building blocks for messages and vast, interactive workflows. And, build messages better with Block Kit Builder.
We're limiting legacy tester tokens by revoking them when they're left unused for several months. As a pleasant counterpoint, our method testers let you bring your own token now.
Apps endure, even when their installing user leaves the team—as long as the app doesn't perform actions on behalf of the installing user. Read up on the new behavior, which rolls out to free, paid, and Enterprise Grid teams over the next week.
Conversation objects associated with shared channels now feature a conversation_host_id field, indicating the workspace or Enterprise Grid organization that "hosts" the shared channel.
We're erasing the shares attribute from "shared channel" conversation objects. In methods like conversations.history and the Events and RTM APIs, enjoy a lighter-weight list of the shared_team_ids representing the teams across which the conversation is shared.
Post replies in a thread with incoming webhooks: the thread_ts parameter now puts your webhook reply in its proper place.
The data structure of messages received from our APIs will change with the launch of Block Kit early next year. In return you'll be able to add newer, clearer visual components to make your app's messages magnificent. Even if you aren't using it, your apps may be affected by the additions. Learn more.
Apps may now restrict Web API requests to as many as 10 IP address ranges. Learn more about IP allowlisting for internal integrations.
The developer preview for workspace apps has ended. We're taking the components of workspace apps and breaking them apart: applying them in phases to existing as well as new apps. Read more about the motivation behind ending the preview.
As public channels become private, they now retain their original channel ID. Legacy methods like groups.* and channels.* don't support these transitional channel types and Conversations API methods must be used instead. Learn more.
Whatever flavor of workspace token you're using, you can now expect the same invalid_auth error code when the token is invalid. You'll receive this error whether the token is expired, revoked, or just plain wrong. Use our OAuth 2.0-based token refresh system to refresh expired tokens safely.
Workspace apps may now continuously rotate shorter-lived tokens without downtime. Our OAuth 2.0-based token refresh system is strongly recommended for all workspace apps. Expiring and rotating tokens is required for all distributed workspace apps.
Clear clever custom statuses like clockwork. Learn how apps can add expiration dates when setting custom statuses for people.
We're postponing planned changes around scope requirements for app and bot access to email addresses. The new date is in autumn, on October 16th, 2018. If you haven't already prepared, read on.
Verifying requests from Slack just got easier: our Node Interactive Messages SDK, Node Events API SDK, and Python Events API SDK now verify request signatures automatically. Learn more.
"40k ought to be enough characters for any message." - Slack Platform Gatekeepers. Messages are now limited to 40,000 characters. Learn more about these planned changes.
Your workspace app can use the new apps.uninstall method to uninstall itself from a single workspace, revoking all tokens associated with it. To revoke a workspace token without uninstalling the app, use auth.revoke.
It's official: workspace apps can reach out to and converse with anyone using the new conversations.app_home:create scope. No more fumbling with conversation IDs or different methods: just plug the user's ID into chat.postMessage and go.
We updated our Slack App Developer Policy and API Terms of Service to provide more detailed guidance, but we have not made material changes. The new policy is effective August 31, 2018. Together, we keep Slack a safe, private and secure platform for work. Learn more.
Pagination rules the nation and the Slack API. These methods newly support cursors: files.info, groups.list, im.list, mpim.list, reactions.list, and stars.list. For apps created after August 7, 2018, results will be returned in perfect, piecemeal pages by default. Learn more about pagination.
With Slack developer tools you can now quickly look up documentation, investigate the structure of messages, and more, all inside of Slack.
Commenting on files is now just like replying to a message. All developers working with file objects, events, or comments should read on to learn more, much more, about file threads.
HTTP requests originating from Slack now support Mutual TLS. Use Mutual TLS to attain the highest level of confidence that requests from Slack are, in fact, authentic. Read more.
Get ready to lend users a hand and start working on their behalf. Now workspace apps can ask for permission to read & write personalized settings like reminders, custom status, and profile data. Learn more about working for users.
Our recently launched message actions are now available for use in all Enterprise Grid workspaces and any Shared Channels within them.
Confidently verify a request originates from Slack by validating our new request signatures. The signing process replaces the use of verification tokens, now deprecated. Learn more.
We expect file threads to arrive after July 19, 2018. Do you manage a Slack app relying heavily on files or file comments? Join our pilot program and prepare your app for file threads ahead of the transition. Learn more about what's changing.
Learn when private channels are deleted with the new group_deleted event, now available for the Events and RTM APIs.
The Conversations API now supports workspace apps, using three simplified scopes: conversations:history, conversations:read, and conversations:write. We recommend upgrading your apps in developer preview to the Conversations API as soon as possible. Learn more.
Beginning October 16, 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.
Adding contextual actions lets users send specific messages to your app at will. Here are some amazing things our partners do with actions. This blueprint demonstrates the ineffable synergy of using actions and dialogs together.
We're compiling a humble library of JSON schema about the Events API into a kind of open specification called AsyncAPI.
Newly-issued bot user token strings are a little longer than before. Building for the ages? Plan for token strings containing up to 255 characters.
Apps participating in our developer preview using the Events API will need to subscribe to message.app_home events for a focused feed of messages between your app and the people who interface with them through the app home. These messages aren't delivered to message.im subscriptions now. Learn more.
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.
Measure drop off and send helpful follow ups when users cancel dialogs with these opt-in cancellation notifications.
Have a bot user token you don't need or want to use anymore? Now you can use xoxb- tokens with auth.revoke.
We're still tidying up the character limits on the text field of posted messages and gradually lowering its maximum. On April 25th, 2018, we began truncating messages greater than 500,000 characters. As of July 12 2018, the maximum is 100,000. We'll begin truncating messages greater than 40,000 characters in August. Learn more.
Your workspace token-based apps in developer preview must now request the files:write scope to upload & manage files instead of files:write:user. Existing access grants are backfilled. Know your read & write rights.
Working with workspace token-based apps as part of our preview? Please start using oauth.access instead of oauth.token during installation. Read on to learn why and about new features.
We corrected and clarified the behavior of users.profile.set to only allow admins of paid teams to update email address profile fields.
We added a type field to the requests dispatched to your Options Load URL, used in message menus and— well, it doesn't work anywhere else yet but we'll have a dialog about that one day...
This significant upgrade to the Slack SDK for Node.js modernizes one of the most widely-used Javascript libraries on our platform with strong typing, more intuitive method signatures, and comfortingly predictable release cycles. It also sheds its aging DataStore, which has not evolved in tandem with the realities of building apps for today's workspaces. Learn more about upgrading in our announcement.
We are continuing to decrease the maximum number of results returned by members arrays returned in channels.* and rtm.start, with the limit currently set to 500 results. conversations.members provides paginated access instead. Read this announcement for detail.
Web API methods will be enhanced with tiered rate limiting beginning March 7, 2018, with most methods gaining greater limits than ever before. Learn more about this week's incremental rollout of rate limit tiers.
Now you can follow up after users submit your dialogs. Use the new response_url attached to any dialog_submission to send messages after submission.
Now users can respond to dialog textarea elements with up to 3,000 riveting, carefully-chosen characters.
Events API rate limiting has matured, now allowing apps up to 30,000 event deliveries per workspace per hour. Having trouble keeping up? Event deliveries will only be disabled when apps drop below a 5% successful response rate. Learn more.
The users.setActive method was recently rendered irrelevant by our efforts to modernize our message servers. Use users.setPresence and/or connect via RTM to proclaim a user's presence instead. We'll remove this no-op method entirely on May 8, 2018.
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.
Having trouble connecting to the RTM API lately? WebSocket URIs may contain querystring parameters & some libraries don't like that. Find out more.
Workspace token apps in developer preview now must request the chat:write scope to post messages. Existing access grants are backfilled. Read on, developer previewers!
Active listening made easier: Subscribe to app_mention events to exclusively receive messages mentioning your app or bot.
Now shared channels can be made private and the implications are well worth considering, especially if assuming channel IDs beginning with C are public. Read on.
For those moments when your app knows a user's email address but hasn't met them on Slack yet: now apps with users:read.email can use users.lookupByEmail and skip wading through users.list.
Storyboard, mock, and play make believe with these useful design templates starring your favorite platform features.
When a workspace migrates to Enterprise Grid, existing users are given a second global user ID. Now you can bulk convert those with migration.exchange and turn off your app's translation layer, living the dream of one user ID per user.
Do what you like with this OpenAPI 2.0 specification of our Web API. Most methods now contain more helpful response examples. More specs and coverage on the way. Read on about our API spec.
Send JSON when posting to Web API write methods. Gone are the days of perfunctory errors when sending lovingly crafted JSON to chat.postMessage and other methods. Read on.
We broadened support for presenting your tokens as a "bearer token" in Authorization HTTP headers with the Web API. Learn more.
We removed the latest, unread_count, and unread_count_display fields from limited contexts of the new Conversations API. They weren't really supposed to be there. You won't find them spuriously lurking in the shadows again. We don't anticipate any issues but let us know if you find any.
The members array found in many API methods is now truncated. We continue to lower the maximum results returned. Please use conversations.members to manage memberships instead. Read on to learn more.
Scheduled changes and feature retirements to the Slack platform are now easier to find in our forward-looking calendar of upcoming changes.
The RTM API's presence_change event requires presence_sub subscriptions beginning November 15, 2017. Read on.
Now you can customize your app's experience by the locale and language preferred by users, channels, and other conversational constructs. Start practicing your Klingon. 🖖 Learn how.
The Conversations API is a collection of more than 15 Web API methods normalizing the way apps deal with channels, direct messages, and more. Never rely on the first character of a channel ID again.
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.
We are clarifying two terms encountered throughout Slack, "team" (the people you talk to in Slack) and "workspace" (the place you do work). You'll find many team references updated to workspace across Slack and API documentation. With artifacts like the team object, field, and parameters scattered through the platform, you'll often still encounter team while reading and programming.
No more sad panda 🐼 because we fixed it — Now the outgoing webhook response payload includes a thread_ts attribute so you know if the message is triggered in a thread!
Batten down the hatches! Further secure your internal integrations by restricting token use of Web API methods to specific IP addresses you trust: IP allowlisting is here.
Improve your custom unfurling flows with these enhancements to authenticated unfurls and chat.unfurl.
No longer the sole domain of slash commands and interactive messages, now apps can emit their own ghostly ephemeral messages with chat.postEphemeral.
Temporary rollback: We've reinstated access to the email attribute for bot and user tokens. On August 1, 2017 we proceeded with limiting email access to user tokens with users:read.email, originally announced in November 2016 and again, with a revised plan in April 2017.
Our developer preview for a new kind of Slack app based on workspace tokens is open. Learn how to work with workspace tokens and about our new Permissions API. Our announcement covers the story behind the token.
With so many token types decorating our platform, this guide to token types has become a necessity.
Now we allow you to learn more about OAuth permission scopes and methods, events, and token types each supports with this helpful OAuth scope library.
Shuttle Slack app installers to the installation flow more swiftly from the Slack Marketplace with a Direct Install URL.
Buried somewhere in this RTM announcement, we told you about the latest field departing from channel objects returned in the long rtm.start preamble. Those fields are gone. Turns out we also removed unread_count_display and unread_count too. If you're suffering from a sense of loss over these unread count fields, please drop us a line. You can still find them in conversations.info.
We're introducing a unified cursor-based pagination model to many of our Web API methods beginning with but one: now you can drink from users.list one delicious sip at a time.
Get an event when more members join your User Group or when — uh-oh, it loses members with subteam_members_changed.
Do you work with presence_change events in the RTM API? Learn about new ways to subscribe and consolidate presence events here.
We've compiled a collection of Best Practices around building fantastic Slack app user experiences. Your users will be stoked!
We've turned a light on for you and your development team: App Blueprints are like recipes for building the internal integrations your team needs to succeed.
Just like subscribing to your app's own newsletter: App Events tell the story of your app's lifecycle. Learn when your app is uninstalled with app_uninstalled, or when user and bot tokens are revoked with tokens_revoked. Pause and resume activity when teams migrate to Enterprise Grid with grid_migration_started and grid_migration_finished.
We undocumented the mysterious user_id_mapping_old_to_new field described in the Enterprise Grid documentation. It doesn't actually exist and never has, oops!
Slackbot wants to help spread the word about your cool Slack app. Add a little HTML to your site and we'll suggest your app when your links are mentioned. Learn how to make your app discoverable.
You'll soon see fewer message.channel_join and message.channel_leave message subtype events in the Events API and RTM API. Instead, you'll find these new refreshingly direct and informative events: member_joined_channel and member_left_channel. Here's the whole scoop.
The old channels.list API method has a new parameter: exclude_members. Some teams are so big and some channels have so many members that listing them all in a single API response along with every other channel is just outright impractical. Cull unneeded data easily accessed with conversations.info by excluding members fields.
We'd like you to stop using rtm.start and start using rtm.connect instead. rtm.connect boots quickly and works well with the most gigantic teams and enterprises of the galaxy.
It's spring cleaning time for email. We're winding down the grandfathering introduced for apps using users:read created before January 4th, 2017. After August 1st, 2017 your apps must request users:read.email to gain that access. See this post for more detail. This retirement has been delayed with no date yet rescheduled.
Observe the custom status of team members with users.profile.get. Update a user's custom status with users.profile.set. Learn how to sync status with calendars, cubicles, conference calls, and bathroom stalls.
More ways to make messages interactive than before: introducing message menus. Define your options statically, dynamically, even personally — or use our handy conversation, channel, and user pickers. Don't forget your field guide.
As with the humans operating them, user objects change over time. With the new updated field, decisively learn last time a user object transformed. Look for it in methods including (but not limited to) users.list and users.info. It's an integer value depicting seconds since the epoch.
We're introducing new, multimedia ways for bots and apps to express themselves in the Slack Marketplace. Follow our new guidelines to make a great impression with potential installers.
Provide users posting links with all the context and interactivity they need, right in Slack. Introducing Slack app unfurling. Here's the announcement!
Beginning March 9, 2017, events transmitted via the Events API will include event_id and event_time fields. event_id is globally unique across all teams while the event_time is when the event dispatched, in integer-based epoch time. Use these fields as you like, but there's nothing you need to do to prepare for this eventuality.
We made it easier to create and manage your Slack apps. And if you're building internal integrations for your own team, there's a better way to install your app without worrying about the OAuths. Check it out.
Looking for custom integrations? They're documented as legacy now. They still work like you're used to but we'd prefer you built your internal integrations as part of a Slack app instead.
Minor field changes coming to channels.history file messages and skype user profile fields. Read all about it.
You have the tools and the talent — now you have the opportunity: Learn how to develop for Slack Enterprise Grid. Here's the announcement for the suits.
Now your app can read, write, and party with message threads. Rolling out to teams over the next few days, message threads are a perfect place to tuck your wonderful workflows. Here's our announcement.
This new year's resolution is a minor slash command revolution: a backwards-compatible, familiar, and decisive means to resolve user IDs, channel IDs, and links from references in slash command invocations. Learn how to turn on this helpful, long-requested feature.
Now everyone's bot is present and accounted for. Events API-only bots can toggle online presence by visiting their app management command center. Details worth catching up on: bot user presence.
We made it so Slack apps have a profile within Slack like humans do — Here's an announcement tweet.
Let's extend a warm welcome to new app_id fields now appearing in our APIs. app_id is now found in rtm.start & bots.info. You'll also find app_id in the bot_added & bot_changed events. What's an app_id? It's the alphanumeric string found in the URL bar while managing your Slack apps.
We've added a new OAuth permission scope called users:read.email. Apps created after January 4th, 2017 will need to request this additional scope to gain access to team member email fields when using users.list and users.info. Existing Slack apps with users:read are automatically grandfathered to include these fields. Here's even more detail on that.
Now you'll find links to practical tutorials and thoughtful articles displayed beside relevant documentation found here on api.slack.com. Discover new articles or browse them by topic in our new Tutorials hub. Written something great? Tell us about it!
Our developer relations team has renewed Slack's adoption of key open source tooling: Slack Developer Kits. Discover our Python & node.js SDKs in their new home on our community index.
Your elaborate Slack apps are no longer shackled to but just one team member. Now you can invite other team members to be App Collaborators to share in the fun and responsibility. Here's what our web log has to say about it: Build together with App Collaborators
We will soon add an additional response_metadata node to our JSON responses; we'll put warnings there first and other useful stuff later. More details are available.
Newly issued OAuth token strings are longer than they were before, as we informed you about last month. Let us know if this vexes you.
Now you can use the users.profile:write OAuth permission scope to reset and upload profile images using users.deletePhoto and users.setPhoto.
We've dramatically improved the process of submitting a Slack App for inclusion in our Slack Marketplace. You'll find a helpful, interactive checklist when first submitting your app. When you're ready to iterate further, you can create a secondary beta application. If a core piece of your app's functionality changes (like requesting new OAuth permission scopes), we'll happily review your app again. Read all about it on the platform blog.
Ever needed to send a user to Slack directly from your app? Here's how to deep link and make native Slack clients part of your app's workflow: Open key teams, channels, and conversations. Or, defer to search results using the slack:// URI scheme.
The character length of token strings is getting longer. Find out how long they'll get and how to future-proof yourself for changes in the future.
You may encounter an occasional user ID beginning with the letter W. We've released a new version of node-slack-sdk to correct a related bug. Read more about these changes.
Introducing the Events API, a new way for Slack apps to receive event types previously available only to the real time messaging API. Subscribe to the events your app needs and have them delivered right to your server as they happen. Build a bot or event-driven app without worrying about websockets, and scale it like a web app. Read more about the Events API in our blog post, Subscribe to the Events API.
Until now, it's been easy to accidentally send messages flush with hundreds of message attachments. We've begun limiting the number of message attachments per message to 100. For approaches like chat.postMessage, incoming webhooks, and chat.update, and response_urls you will receive a too_many_attachments error. Unfortunately, we are unable to serve you an error when sending messages as part of a slash command or message buttons invocation response.
If you're interested in listing your Slack app in the Slack Marketplace, you'll want to review our new Slack Marketplace Agreement and consider our Security Review Process. Find these and other policies in our new Slack App developer policy hub.
We've corrected a bug where incoming webhooks could post messages in "#general" even 1) if that channel restricts posts and 2) the user owning the webhook was not allowed to post there. This new behavior will only prevent recently created webhooks from posting to restricted "#general" channels, so if your old webhooks are relying on this quirk, they'll be fine for now.
Now your applications can read and write defined team profile fields for individual team members. The users.profile:write scope allows you to edit fields with users.profile.set. The users.profile:read scope empowers you to discover available fields with team.profile.get and retrieve user profiles with users.profile.get.
Slack apps can now add action-invoking interactive buttons to messages, allowing you to simplify workflows and encourage users to take decisive action from within Slack.
We've corrected the behavior of stars.list so that it only returns stars belonging to the owner of the presented token. The user parameter may still be used if the provided user ID belongs to the user utilizing the token.
Team administrators may now use tokens with the admin scope to request information about the billable status of team members using the team.billableInfo API method.
Now that bot_id appears in the real-time messaging API and Web API, you need a better way to look up bot users. Use the new bots.info method to query bot/application information by ID. It requires the users:read scope.
Additional real time messaging API events will begin including the event_ts timestamp field later this summer. Find out what to expect.
Now you can put down a footer on your message attachments. Use the footer, footer_icon, and ts fields to tie content across time and space.
For the few of you out there using outdated tokens, we've made some changes to authorship behavior when using chat.postMessage.
Error conditions in incoming webhooks are due for an improvement. Read all about how blanket HTTP 500s will become more fine-grained, purposeful error conditions. Shipped on June 16, 2016.
Recently introduced bugs in our iOS & Android apps cause message attachment fields marked as "short" to wrongly render long anyway. Our fixes may take a couple weeks to reach each platform.
Sign team members into your website, service, or application with Sign in with Slack, based on the same OAuth 2.0 flow used by the Add to Slack button. Read more about it in this announcement.
We've added two new API methods: users.identity works with Sign in with Slack and auth.revoke revokes hallway privileges for access tokens. Actually, it revokes the whole token.
Bot user tokens may now use files.info to look up information about files they have access to by virtue of their channel memberships. Also, very helpful for adapting to upcoming file events changes.
File events are changing in the real time messaging API beginning May 16th, 2016. Here are details on everything that will change, and the upcoming ability for files.info to be used by bot users.
As previously announced, we've added a bot_id field to relevant API responses. Let us know if you run into any issues.
We released a family of API methods to create and manage reminders. Meet reminders.list, reminders.info, reminders.add, reminders.delete, and reminders.complete.
We fixed an unfortunate bug where a team member could inadvertently uninstall a whole Slack App from their team by removing a single incoming webhook associated with that instance of the app.
Your bot users author their own messages, now they can edit them too. Bot user tokens may now use chat.update, like humans do.
Now chat.postMessage will better intuit your intent when you don't explicitly specify the as_user parameter. Let us know if we're guessing wrong!
One day soon our Web API will warn you when something is only slightly wrong with your requests. Read all about API warnings.
Be welcoming. Be kind. Look out for each other. This is the Code of Conduct for the Slack Developer community.
Now bot users can use methods requiring the dnd:read scope, like dnd.info and dnd.teamInfo. Your bots'll be more polite than a protocol droid!
Users can now rename Bot Users they've installed as Slack Apps. More naming, more claiming. No more terrible twos.
We finally updated the slackhq/slack-api-docs repository, reflecting recently introduced and quite ancient documentation updates and new features.
reaction_added & reaction_removed events now include an item_user field indicating the user that created the original content everyone's raving about.
Published this changelog you're reading right now. So that you can know about all this stuff. Tell your friends.
New Web API methods: share files publicly with files.sharedPublicURL or make them private again with files.revokePublicURL.
files.comments.add, files.comments.edit, and files.comments.delete are now available to bot users.
Quickly find the right tools for your project with our new listing of often-used open source libraries.
The handy test token generator previously found in the Web API documentation now stands proud with its very own page.
Make sure you're ready before submitting your Slack App for review by following this Slack app checklist.
Incoming Webhooks documentation updated to better bait best practices and discourage fishy formatting behavior.
Now you can upgrade your Slack App's OAuth Scopes by managing your apps. This article explains it all.
You can now package Bot Users within Slack Apps, making your creations easier to distribute to teams.
We announced the Slack Fund to "give developers the backing they need to build everything possible in Slack."
Enjoy major updates to the Slash Commands documentation, expanding on topics like... delayed responses.
More granular OAuth scopes are here! Now your apps can ask for the exact level of access you need.