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 not signed into any teams. Sign in to test authentication.

This method allows you to exchange a temporary OAuth code for an API access token.

This is the third step of the OAuth authentication flow.

We strongly recommend supplying the Client ID and Client Secret using the HTTP Basic authentication scheme, as discussed in RFC 6749.

If at all possible, avoid sending client_id and client_secret as parameters in your request.

Keep your tokens secure. Do not share tokens with users or anyone else.

When used with a legacy workspace app, this method's response differs significantly. It may be used as part of the initial OAuth authentication flow to gain a long-lived refresh token and short-lived access token, or it may be used subsequently to refresh the access token.


Argument Example Required Description
client_id 4b39e9-752c4 Required

Issued when you created your application.

client_secret 33fea0113f5b1 Required

Issued when you created your application.

code ccdaa72ad Required

The code param returned via the OAuth callback.

redirect_uri Optional

This must match the originally submitted URI (if one was sent).

single_channel true Optional, default=false

Request the user to add your app only to a single channel.

Present arguments as parameters in application/x-www-form-urlencoded querystring or POST body. This method does not currently accept application/json.


The response schema for this step of OAuth differs depending on the scopes requested and the type of application used. When asking for the bot scope, you'll receive the token separately from the user token.

Successful user token negotiation for a single scope

    "access_token": "xoxp-XXXXXXXX-XXXXXXXX-XXXXX",
    "scope": "groups:write",
    "team_name": "Wyld Stallyns LLC",
    "team_id": "TXXXXXXXXX"

Success example when asking for multiple scopes, a bot user token, and an incoming webhook

    "access_token": "xoxp-XXXXXXXX-XXXXXXXX-XXXXX",
    "scope": "incoming-webhook,commands,bot",
    "team_name": "Team Installing Your Hook",
    "team_id": "TXXXXXXXXX",
    "incoming_webhook": {
        "url": "",
        "channel": "#channel-it-will-post-to",
        "configuration_url": ""
    "bot": {
        "bot_user_id": "UTTTTTTTTTTR",
        "bot_access_token": "xoxb-XXXXXXXXXXXX-TTTTTTTTTTTTTT"

Success example using a workspace app produces a very different kind of response

    "ok": true,
    "access_token": "xoxa-access-token-string",
    "token_type": "app",
    "app_id": "A012345678",
    "app_user_id": "U0NKHRW57",
    "team_name": "Subarachnoid Workspace",
    "team_id": "T061EG9R6",
    "authorizing_user": {
        "user_id": "U061F7AUR",
        "app_home": "D0PNCRP9N"
    "installer_user": {
        "user_id": "U061F7AUR",
        "app_home": "D0PNCRP9N"
    "scopes": {
        "app_home": [
        "team": [],
        "channel": [
        "group": [
        "mpim": [
        "im": [
        "user": []

Typical error response

    "ok": false,
    "error": "invalid_client_id"

Legacy workspace app behavior

Workspace apps may call oauth.access in two different scenarios.

  1. Upon receiving a temporary authorization code during the OAuth flow, the app calls this method to gain a refresh token and a short-lived access token.
  2. Subsequently, a workspace app calls this method in order to gain a new access token, passing the refresh token as argument and grant_type=refresh_token as a parameter.

Read more about the refresh token and access token split.

Here's a primer on the fields you will initally receive as a workspace app calling this method:

  • access_token - Your access token for this workspace. The token string begins with xoxa-2 and can be very long. When automatic expiration is turned on, this token will expire after the duration specified in expires_in. After that it must be refreshed using a refresh_token and token rotation.
  • refresh_token - Your refresh token for this workspace. The token string begins with xoxr. Use this token to refresh a short-lived access_token by following the token rotation instructions.
  • expires_in - This integer tells your app how long the access token is valid for, in seconds.
  • token_type - You'll see app here. Workspace tokens were once known as app tokens. Maybe someday this value will become workspace.
  • app_id - This is the unique ID for your whole Slack app.
  • app_user - This is the user ID of your app. It's a user! It's an app! It's a user! It's an app! The user ID is unique to the team installing it.
  • installer_user - This node holds the user_id of the user that originally installed this app. It also contains the app_home conversation ID for that same user.
  • authorizing_user - This node contains the user_id and app_home converation ID of the user currently navigating through the authorization process. It might be different than the original installer.
  • team_name - This is what the team calls itself.
  • team_id - This is the unique ID for the team.
  • permissions - This field is no longer available. Use to look up all of your app's permissions for this workspace instead.
  • scopes - All OAuth scopes awarded to your app — not just those awarded this authorization attempt.
  • single_channel_id - if this app is approved for a single channel, that channel will be listed here. See single channel authorizations for more info.

A quick note on rate-limiting: oauth.access follows a custom rate-limiting scheme for the refresh case only. After your app has received its refresh token, it may call the endpoint with grant_type=refresh_token to gain a new access token at a rate of 10 calls per minute, with an occasional burst of up to 50.

Use to look up your app's permissions on the fly.

Scopes categorized by resource

Scopes are grouped by resource type:

  • app_home - your app's direct message conversation with the installer of this app
  • team - team-level permissions assigned to your app
  • channel - public channels
  • group - private channels
  • mpim - multi-member direct messages
  • im - direct messages
  • user - permissions to work with or as specific users

The Permissions API describes in more detail how resources and scopes work together to enforce what your app can do.


This table lists the expected errors that this method could return. However, other errors can be returned in the case where the service is down or other unexpected factors affect processing. Callers should always check the value of the ok params in the response.

Error Description

Value passed for client_id was invalid.


Value passed for client_secret was invalid.


Value passed for code was invalid.


Value passed for redirect_uri did not match the redirect_uri in the original request.


The method was passed an argument whose name falls outside the bounds of accepted or expected values. This includes very long names and names with non-alphanumeric characters other than _. If you get this error, it is typically an indication that you have made a very malformed API call.


The method was passed a PHP-style array argument (e.g. with a name like foo[7]). These are never valid with the Slack API.


The method was called via a POST request, but the charset specified in the Content-Type header was invalid. Valid charset names are: utf-8 iso-8859-1.


The method was called via a POST request with Content-Type application/x-www-form-urlencoded or multipart/form-data, but the form data was either missing or syntactically invalid.


The method was called via a POST request, but the specified Content-Type was invalid. Valid types are: application/x-www-form-urlencoded multipart/form-data text/plain.


The method was called via a POST request and included a data payload, but the request did not include a Content-Type header.


The workspace associated with your request is currently undergoing migration to an Enterprise Organization. Web API and other platform operations will be intermittently unavailable until the transition is complete.


The method was called via a POST request, but the POST data was either missing or truncated.


The server could not complete your operation(s) without encountering a catastrophic error. It's possible some aspect of the operation succeeded before the error was raised.


This table lists the expected warnings that this method will return. However, other warnings can be returned in the case where the service is experiencing unexpected trouble.

Warning Description

The method was called via a POST request, and recommended practice for the specified Content-Type is to include a charset parameter. However, no charset was present. Specifically, non-form-data content types (e.g. text/plain) are the ones for which charset is recommended.


The method was called via a POST request, and the specified Content-Type is not defined to understand the charset parameter. However, charset was in fact present. Specifically, form-data content types (e.g. multipart/form-data) are the ones for which charset is superfluous.

This method cannot be used with the tester at this time.