Get a user's identity.

Facts

Method access

HTTP
JavaScript
Python
Java
HTTP
GEThttps://slack.com/api/users.identity
Bolt for Java
app.client().usersIdentity
Powered by Bolt
Bolt for Python
app.client.users_identity
Powered by Bolt
Bolt for JavaScript
app.client.users.identity
Powered by Bolt

Content types

application/x-www-form-urlencoded
  • Rate limits

    Tier 3
  • Arguments

    ArgumentTypeDescription
    tokenRequired

    Authentication token bearing required scopes. Tokens should be passed as an HTTP Authorization header or alternatively, as a POST parameter.

    Examplexxxx-xxxxxxxxx-xxxx

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

    Example responses

    Common successful response

    You will receive at a minimum the following information:

    {
        "ok": true,
        "user": {
            "name": "Sonny Whether",
            "id": "U0G9QF9C6"
        },
        "team": {
            "id": "T0G9PQBBK"
        }
    }
    Alternate response

    The identity.email scope provides the member's email address, if available:

    {
        "ok": true,
        "user": {
            "name": "Sonny Whether",
            "id": "U0G9QF9C6",
            "email": "bobby@example.com"
        },
        "team": {
            "id": "T0G9PQBBK"
        }
    }
    Alternate response

    Using with the identity.avatar scope yields the member's avatar images. Available sizes may vary in the future.

    {
        "ok": true,
        "user": {
            "name": "Sonny Whether",
            "id": "U0G9QF9C6",
            "image_24": "https://cdn.example.com/sonny_24.jpg",
            "image_32": "https://cdn.example.com/sonny_32.jpg",
            "image_48": "https://cdn.example.com/sonny_48.jpg",
            "image_72": "https://cdn.example.com/sonny_72.jpg",
            "image_192": "https://cdn.example.com/sonny_192.jpg"
        },
        "team": {
            "id": "T0G9PQBBK"
        }
    }
    Alternate response

    Use with the identity.team scope to retrieve the user's workspace name:

    {
        "ok": true,
        "user": {
            "name": "Sonny Whether",
            "id": "U0G9QF9C6"
        },
        "team": {
            "name": "Captain Fabian's Naval Supply",
            "id": "T0G9PQBBK"
        }
    }
    Common error response

    Typical error response

    {
        "ok": false,
        "error": "account_inactive"
    }

    After your Slack app is awarded an identity token through Sign in with Slack, use this method to retrieve a user's identity.

    The returned fields depend on any additional authorization scopes you've requested.

    With traditional Slack apps, this method must be called by individual user tokens with the identity.basic scope, as provided in the Sign in with Slack process.

    Note: When users sign into Slack via Apple, their emails appear as anonymized relay addresses. Sign in with Slack won't work with these users.

    User IDs are not guaranteed to be globally unique across all Slack users. The combination of user ID and team ID, on the other hand, is guaranteed to be globally unique.

    See the Sign in with Slack docs for even more information on these responses.

    In addition, you can request access to additional profile fields by adding the following authorization scopes to your OAuth request, detailed in the above examples.

    Errors

    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.

    ErrorDescription
    invalid_user_id

    Invalid user id provided

    user_not_specified [hidden]user not specified (generated)
    not_authed

    No authentication token provided.

    invalid_auth

    Some aspect of authentication cannot be validated. Either the provided token is invalid or the request originates from an IP address disallowed from making the request.

    account_inactive

    Authentication token is for a deleted user or workspace when using a bot token.

    token_revoked

    Authentication token is for a deleted user or workspace or the app has been removed when using a user token.

    token_expired

    Authentication token has expired

    no_permission

    The workspace token used in this request does not have the permissions necessary to complete the request. Make sure your app is a member of the conversation it's attempting to post a message to.

    org_login_required

    The workspace is undergoing an enterprise migration and will not be available until migration is complete.

    ekm_access_denied

    Administrators have suspended the ability to post a message.

    missing_scope

    The token used is not granted the specific scope permissions required to complete this request.

    not_allowed_token_type

    The token type used in this request is not allowed.

    method_deprecated

    The method has been deprecated.

    deprecated_endpoint

    The endpoint has been deprecated.

    two_factor_setup_required

    Two factor setup is required.

    enterprise_is_restricted

    The method cannot be called from an Enterprise.

    is_bot

    This method cannot be called by a bot user.

    invalid_arguments

    The method was either called with invalid arguments or some detail about the arguments passed are invalid, which is more likely when using complex arguments like blocks or attachments.

    invalid_arg_name

    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.

    invalid_array_arg

    The method was passed an array as an argument. Please only input valid strings.

    invalid_charset

    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.

    invalid_form_data

    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.

    invalid_post_type

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

    missing_post_type

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

    team_added_to_org

    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.

    invalid_json [hidden]The method was called via a `POST` request with `Content-Type` `application/json`, but the body was not valid JSON.
    json_not_object [hidden]The method was called via a `POST` request a valid JSON body, but the JSON value was not an object.
    ratelimited

    The request has been ratelimited. Refer to the Retry-After header for when to retry the request.

    accesslimited

    Access to this method is limited on the current network

    request_timeout

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

    upgrade_required [hidden]The calling application needs to be upgraded.
    service_unavailable

    The service is temporarily unavailable

    fatal_error

    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.

    internal_error

    The server could not complete your operation(s) without encountering an error, likely due to a transient issue on our end. It's possible some aspect of the operation succeeded before the error was raised.

    Warnings

    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.

    WarningDescription
    missing_charset

    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.

    superfluous_charset

    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.

    Arguments

    Need a token? Create and install a Slack app to begin.
    This will make a real API request. Beware of using it with live workspaces.

    API response


    Submit your arguments to see the API response

    Was this page helpful?