Unlock your productivity potential with Slack Platform
Be inspired
Get a fast start with samples and tutorials for common use cases.
Build Slack apps
Customize your Slack experience with apps using a wide range of APIs.
Your work just works, on any device
Block Kit lets you build interfaces without a UI designer. It's available for use in surfaces across all devices without any extra code.
Stay up-to-date
We'd like to add additional clarity to the recent rate limits change for the conversations.history and conversations.replies Web API methods. Any internal customer-built apps created before May 29th, 2025 will maintain their existing rate limits and will not be subject to the new posted limits. Read the updated FAQ for more info, and please continue to reach out with questions!
We're making clarifications to the API Terms of Service that will take effect immediately for new apps and on June 30, 2025 for existing apps. Please read the terms in full, but below is a summary of what’s changing:
- Commercial Distribution: The updated terms confirm that the Slack Marketplace is the only appropriate channel for commercially distributing apps built with Slack APIs, whether those apps are unlisted (published outside of the Marketplace) or templatized one-off "custom" apps.
- Data Usage Restrictions: We're reinforcing safeguards around how data accessed via Slack APIs can be stored, used, and shared.
- API-Specific Terms: We're providing clearer guidance on how to use certain APIs, such as the Discovery API and the Data Access API, responsibly.
We're updating the rate limits for the conversations.history and conversations.replies Web API methods methods for non-Marketplace apps. This rate limit reduction will immediately affect new applications and new installations of non-Marketplace applications. The new rate limits will be applied to existing installations of unlisted, distributed applications published outside the Marketplace on September 2, 2025. The new rate limits will be updated to allow 1 request per minute and will return a maximum of 15 objects per request. Read more here.
Version 3.2.0 of the developer tools for the Slack platform is here!
- * We now display the manifest source as human-friendly output:
project (local) and app settings (remote). You'll see these changes in the slack create, slack init, and slack app link <id> commands, for example.- The link between your project code and the configurations within app settings can now be accessed by running the
slack app settings command. Bolt developers with a remote manifest source managed within app settings may find this useful for discovering new features or making updates.- We fixed a bug: The example
slack app link and slack app list commands shown when running the slack app --help command now use the entire command in order to prevent potential aliasing errors.- We fixed a bug to improve the console output to handle string values for versions.
Version 3.1.0 of the developer tools for the Slack platform has sprouted!
- We've updated the
slack app link command to work with apps that have a local manifest source.- We've updated the
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.- Related to the above update, the
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.- We've updated the
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.- We've fixed a bug from a rare edge case that caused the Slack CLI to hang without exiting the process. Now, the Slack CLI will exit with the correct error code and allow sub-processes to clean up.
Version 3.0.5 of the developer tools for the Slack platform has bloomed!
- The Slack CLI and installation scripts now point to our new Slack platform documentation at docs.slack.dev and our developer tools documentation at tools.slack.dev.
- As part of the Slack CLI going open source, the Slack CLI documentation has gone open source as well!
- We fixed a bug: When running the
slack upgrade command inside a project directory, the output now notes whether the latest SDK versions were checked.