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


You’re viewing documentation on legacy custom integrations, an older way for teams to build into their Slack team. To securely utilize the newest platform features like message buttons & the Events API, build internal integrations as part of a Slack app just for your team instead. Get started.

The Slack Web API allows you to build applications that interact with Slack in more complex ways than the integrations we provide out of the box.


The Web API consists of HTTP RPC-style methods, all of the form

All methods must be called using HTTPS. Arguments can be passed as GET or POST params, or a mix. The response contains a JSON object, which will always contain a top-level boolean property ok, indicating success or failure. For failure results, the error property will contain a short machine-readable error code. In the case of problematic calls that could still be completed successfully, ok will be true and the warning property will contain a short machine-readable warning code (or comma-separated list of them, in the case of multiple warnings).

    "ok": true,
    "stuff": "This is good"
    "ok": false,
    "error": "something_bad"
    "ok": true,
    "warning": "something_problematic",
    "stuff": "Your requested information"

Other properties are defined in the documentation for the relevant method.


Authenticate your Web API requests by providing a bearer token, which identifies a single user.

While developing or testing your app, you may use test tokens using our test token generator. We don't recommend using test tokens in your custom integrations. Build a Slack app just for your team instead and scope permissions appropriately.

Generate test tokens

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