You must enable javascript in order to use the Slack API Documentation. You can do this in your browser settings.
Go to Slack

Legacy tokens

You're reading this because you're looking for info on legacy custom integrations - an outdated way for teams to integrate with Slack. These integrations lack newer features and they will be deprecated and possibly removed in the future. We do not recommend their use.
Instead, we suggest that you read about their replacement - Slack apps. Slack apps can be built just for your own workspace or distributed through the App Directory, and they can use the latest and greatest APIs and UI features.

Legacy tokens are an old method of generating tokens for testing and development.

Because we strongly recommend you do not use legacy custom integrations anymore, you should instead use Slack apps to quickly generate tokens, without OAuth, by installing your app to your own team.


Migrating from legacy tokens

If you were using a legacy token to make calls with the Web API, you'll need to generate a new one for your new Slack app. If you chose to build a workspace app, you can install it to your own workspace in a couple of clicks. Then prepare it for distribution by following our guide to using OAuth to generate workspace tokens. Traditional Slack apps can follow our guide to the OAuth flow.

For testing and development, you can quickly and easily create a new Slack app and install it in two clicks.

Once it's installed, use the app's settings to progressively add the permission scopes you need for your testing.


Legacy information

Though we recommend that all legacy custom integrations should migrate to Slack apps, we also understand that some will still need to maintain older integrations. This section contains any information about using legacy tokens that is specific to the legacy implementation.

Legacy token generator

Use this tool to generate legacy tokens.

Legacy tokens are just for you. Never share legacy tokens with other users or applications. Do not publish Legacy tokens in public code repositories. Review token safety tips.

By creating a test API token, you agree to the Slack API Terms of Service.

Please log into your workspace and then reload this page to view your tokens.

Legacy token capabilities

Tokens generated with this tool will be associated with the currently signed in user and team.

The tokens will automatically be granted the following scopes:

  • identify - identifies your personal user information like name and team
  • read - allows this token to request data about channels, messages, team members, and more
  • post - allows this token to post content to your channels and perform other write actions like edit your profile
  • client - allows this token to connect to the real time streaming API and perform most actions your user account is capable of throughout the Slack service
  • admin - only attached if the current user is an admin for that team. Allows retrieval and modification of team-wide administrative information.

These tokens provide access to your private data and that of your team. Keep these tokens to yourself and do not share them with others. Tester tokens are not intended to replace OAuth 2.0 tokens.