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

team.profile.get

Retrieve a team's profile.

Supported token types:
Expected scopes:

This method is used to get the profile field definitions for this team.

Arguments

This method has the URL https://slack.com/api/team.profile.get and follows the Slack Web API calling conventions.

Argument Example Required Description
token xxxx-xxxxxxxxx-xxxx Required

Authentication token bearing required scopes.

visibility all Optional

Filter by visibility.

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

The optional visibility argument allows the client to filter the profile fields based on visibility. The following values are supported:

  • all is the default, and returns all fields.
  • visible means return only fields for which the is_hidden option is missing or false.
  • hidden means return only fields for which the is_hidden option is true.

Response

The response contains a profile item with an array of key value pairs. Right now only the fields key is supported, and it contains a list of field definitions for this team.

Note that returned field definitions always have an id.

Typical success response

{
    "ok": true,
    "profile": {
        "fields": [
            {
                "id": "Xf06054AAA",
                "ordering": 0,
                "label": "Phone extension",
                "hint": "Enter the extension to reach your desk",
                "type": "text",
                "possible_values": null,
                "options": null,
                "is_hidden": 1
            },
            {
                "id": "Xf06054BBB",
                "ordering": 1,
                "label": "Date of birth",
                "hint": "When you were born",
                "type": "date",
                "possible_values": null,
                "options": null
            },
            {
                "id": "Xf06054CCC",
                "ordering": 2,
                "label": "Facebook",
                "hint": "Enter a link to your Facebook profile",
                "type": "link",
                "possible_values": null,
                "options": null
            },
            {
                "id": "Xf06054DDD",
                "ordering": 3,
                "label": "House",
                "hint": "Hogwarts, obviously",
                "type": "options_list",
                "possible_values": [
                    "Gryffindor",
                    "Hufflepuff",
                    "Ravenclaw",
                    "Slytherin"
                ],
                "options": null
            },
            {
                "id": "Xf06054EEE",
                "ordering": 4,
                "label": "Location",
                "hint": "Office location (LDAP)",
                "type": "text",
                "possible_values": null,
                "options": {
                    "is_protected": 1
                }
            },
            {
                "id": "Xf06054FFF",
                "ordering": 5,
                "label": "Manager",
                "hint": "The boss",
                "type": "user",
                "possible_values": null,
                "options": null
            }
        ]
    }
}

Typical error response

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

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.

Error Description
not_authed

No authentication token provided.

invalid_auth

Invalid authentication token.

account_inactive

Authentication token is for a deleted user or workspace.

no_permission

The workspace token used in this request does not have the permissions necessary to complete the request.

user_is_bot

This method cannot be called by a bot user.

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 a PHP-style array argument (e.g. with a name like foo[7]). These are never valid with the Slack API.

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/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.

request_timeout

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

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.

Warning Description
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.