Scopes are basically permissions defining which features of Slack you can access. Here you will select the 'scopes' that your 'app' has access to. Click on OAuth & Permissions in the left panelĥ. (If you have multiple workspaces, select one for now and you can distribute the app across the Org later)Ĥ. Enter an app name such as 'Admin API' and select your workspace. Click on 'Build' in the top right, then select 'Create App' and choose 'From scratch'ģ. In your Slack workspace, select your workspace name in the top right, go to Settings & administration > Manage appsĢ. If not, here's another way that is a little more straightforward:ġ.

If you are familiar with OAuth and are comfortable following those steps, feel free to do so. Slack has a great article on setting up a slack app and authenticating Postman using OAuth 2.0. Using the Downloaded Collections Step One - Slack Setup If you are a developer/IT engineer, the Slack guides on creating apps are likely a better source for following best practices, etc. This guide is intended for anyone who may not have experience with APIs or Postman as a tool. This guide will walk you through setting up postman to make changes directly to slack using their public APIs. Sometimes however, there is a problem that can't yet be solved through their admin user interface and it requires a more creative solution, like making changes directly in the backend of the application. Slack is constantly pumping out new admin features and abilities to manage various roles, permissions, and analytics on the platform.

Slack scim api