Skip to main content

admin.conversations.getConversationPrefs method

The features within are only available to Slack workspaces on an Enterprise plan.

Don't have a paid plan? Join the Developer Program and provision a fully-featured sandbox for free.

Facts​

DescriptionGet conversation preferences for a public or private channel.
Method Access
POST https://slack.com/api/admin.conversations.getConversationPrefs
Scopes
Content types
application/x-www-form-urlencoded
application/json
Rate LimitsTier 2: 20+ per minute

Arguments​

Required arguments

tokenstringRequired

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

Example: xxxx-xxxxxxxxx-xxxx
channel_idRequired

The channel to get preferences for.

Example: C12345

Usage info​

This Admin API method retrieves posting permissions for a public or private channel.

You'll receive a list of who_can_post and can_thread, which represent who can post and who can respond in threads.

The above fields may contain a type, which identifies the type of Slack user who can post or thread (for example, admins.) The fields may also directly list users by user ID who have the ability to post or respond in threads.

You may also receive can_huddle, which represents if a huddle can be started in the channel.

You may receive enable_at_channel, which determines whether channel mentions can be used in a channel. If this pref does not exist, then channel mentions are enabled by default. You may receive enable_at_here, which determines whether here mentions can be used in a channel. If this pref does not exist, then here mentions are enabled by default. Both enable_at_here and enable_at_channel determine whether everyone mentions can be used in a general channel. If they do not exist for a general channel, then everyone mentions can be used.

This admin scope is obtained through version two of the OAuth V2 flow, but there are a few additional requirements. The app requesting this scope must be installed by an admin or Owner of an Enterprise organization. Also, the app must be installed on the entire org, not on an individual workspace. See below for more details. If the app is installed by an Org Admin or Owner, ensure the Channel Management settings provide the appropriate permissions. The Org Admin or Owner installing the app must have the Channel Management role, and must also be granted access to Public channels and Private channels within this role. If these criteria aren't met, the Org Admin or Owner will receive a not_allowed error when attempting to install an app.

Admin API endpoints reach across an entire Enterprise organization, not individual workspaces.

For a token to be imbued with Admin scopes, it must be obtained from installing an app on the entire Enterprise org, not just a workspace within the organization.

To configure and install an app supporting Admin API endpoints on your Enterprise organization:

  1. Create a new Slack app. Your app will need to be able to handle a standard OAuth 2 flow.
  2. In the app's settings, select OAuth & Permissions from the left navigation. Scroll down to the section titled Scopes and add the admin.* scope you want. Click the Save Changes button.
  3. In the app's settings, select Manage Distribution from the left navigation. Under the section titled Share Your App with Other Workspaces, make sure all four sections have the green check. Then click the green Activate Public Distribution button.
  4. Under the Share Your App with Your Workspace section, copy the Sharable URL and paste it into a browser to initiate the OAuth handshake that will install the app on your organization. You must be logged in as an admin or Owner of your Enterprise organization to install the app.
  5. Check the dropdown in the upper right of the installation screen to make sure you are installing the app on the organization, not an individual workspace within the organization. See the image below for a visual.
  6. Once your app completes the OAuth flow, you will be granted an OAuth token that can be used for calling Admin API methods for your organization.

When installing an app to use an Admin API endpoint, be sure to install it on your Enterprise organization, not a workspace within the organization.

Response​

Get conversation preferences for a public or private channel.

{
  "ok": true,
  "prefs": {
    "who_can_post": {
      "type": "admin",
      "user": "U1234"
    },
    "can_thread": {
      "type": "admin, owner",
      "user": "U1234,U5678"
    }
  }
}

Get conversation preferences for a public or private channel.

{
  "ok": true,
  "prefs": {
    "who_can_post": {
      "type": [
        "admin"
      ],
      "user": [
        "ABCD4567E"
      ]
    },
    "can_thread": {
      "type": [
        "ra"
      ],
      "user": []
    },
    "enable_at_channel": {
      "enabled": false
    },
    "enable_at_here": {
      "enabled": false
    }
  }
}

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 parameter in the response.

Error
Description
access_denied

Access to a resource specified in the request is denied.

accesslimited

Access to this method is limited on the current network

account_inactive

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

channel_not_found

The value passed for channel_id was invalid.

channel_type_not_supported

The provided channel_id was a DM, MPDM, or the 'general' channel.

could_not_get_conversation_prefs

There was an error getting the conversation preferences for this channel.

deprecated_endpoint

The endpoint has been deprecated.

ekm_access_denied

Administrators have suspended the ability to post a message.

enterprise_is_restricted

The method cannot be called from an Enterprise.

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.

feature_not_enabled

The token provided does not have access to this method.

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.

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_arguments

The method was called with invalid arguments.

invalid_array_arg

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

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.

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.

method_deprecated

The method has been deprecated.

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.

missing_scope

The token provided doesn't have the required scopes.

missing_scope

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

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.

not_allowed_token_type

The token type used in this request is not allowed.

not_an_admin

The token provided is not associated with an Org Admin or Owner.

not_an_enterprise

This endpoint can only be called by an Enterprise organization.

not_authed

No authentication token provided.

org_login_required

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

ratelimited

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

request_timeout

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

restricted_action

A workspace preference prevents the authenticated user from listing preferences.

service_unavailable

The service is temporarily unavailable

team_access_not_granted

The token used is not granted the specific workspace access required to complete this request.

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.

token_expired

Authentication token has expired

token_revoked

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

two_factor_setup_required

Two factor setup is required.