Go to Slack


You're not signed into any teams. Sign in to test authentication.

This method renames a team channel.

The only people who can rename a channel are Team Admins, or the person that originally created the channel. Others will receive a "not_authorized" error.


Argument Example Required Description
token xxxx-xxxxxxxxx-xxxx Required

Authentication token bearing required scopes.

channel C1234567890 Required

Channel to rename

name   Required

New name for channel.

validate true Optional

Whether to return errors on invalid channel name instead of modifying it to meet the specified criteria.

This method supports application/json via HTTP POST. Present your token in your request's Authorization header. Learn more.


Channel names can only contain lowercase letters, numbers, hyphens, and underscores, and must be 21 characters or less. We will validate the submitted channel name and modify it to meet the above criteria. When calling this method, we recommend storing the channel's name value that is returned in the response.


Returns a channel object:

Typical success response

    "channel": {
        "created": 1477445146,
        "creator": "U2U85N1RZ",
        "id": "C2U875RJN",
        "is_archived": false,
        "is_channel": true,
        "is_general": false,
        "is_member": false,
        "is_mpim": false,
        "is_org_shared": false,
        "is_private": false,
        "is_shared": false,
        "members": [],
        "name": "humans-and-bots",
        "name_normalized": "humans-and-bots",
        "previous_names": [
        "purpose": {
            "creator": "U2U85N1RZ",
            "last_set": 1509475801,
            "value": "the purpose of this channel is to bring people and robots together in harmony"
        "topic": {
            "creator": "U2U85N1RZ",
            "last_set": 1509475775,
            "value": "here be robots"
        "unlinked": 0
    "ok": true

Typical error response

    "ok": false,
    "error": "invalid_auth"


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 channel was invalid.


Caller is not a member of the channel.


Caller cannot rename this channel


Value passed for name was invalid.


New channel name is taken


Value passed for name was empty.


Value passed for name contained only punctuation.


Value passed for name exceeded max length.


Value passed for name contained unallowed special characters or upper case characters.


No authentication token provided.


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.


Authentication token is for a deleted user or workspace.


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


This method cannot be called by a bot user.


This method cannot be called by a restricted user or single channel guest.


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.

Argument Value
token Required Generate tokens to test with here.
channel Required
name Required
validate Optional
Extra args