Skip to content
The Desk

Edit a message

PATCH
/channels/{channel}/messages/{message}
curl --request PATCH \
  --url https://desk.example.com/api/v1/channels/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/messages/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0 \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "body": "example" }'

Required scope: messages:write

Only the message’s own author may edit it.

Authorizations

Section titled “Authorizations”

Parameters

Section titled “ Parameters ”

Path Parameters

Section titled “Path Parameters”
channel
required
string format: uuid

The channel’s id.

message
required
string format: uuid

The message’s id.

Request Bodyrequired

Section titled “Request Bodyrequired”
Media typeapplication/json
object
body
required

The replacement text. Surrounding whitespace is trimmed.

string
<= 8000 characters
Examplegenerated
{
  "body": "example"
}

Responses

Section titled “ Responses ”

200

Section titled “200”

The edited message, carrying an edited_at stamp.

Media typeapplication/json
object
data
required
object
id
required
string format: uuid
channel_id
required
string format: uuid
body
required
string
type
required

standard is an authored message; member_joined and member_left are system notices the app writes itself.

string
Allowed values: standard member_joined member_left poll
author
required

A workspace member, human or bot.

object
id
required
string format: uuid
name
required
string
type
required
string
Allowed values: human bot
reply_to_id
required
string | null format: uuid
thread_root_id
required
string | null format: uuid
reactions
required
Array<object>

One emoji and how many members reacted with it.

object
emoji
required
string
count
required
integer
>= 1
created_at
required
string | null format: date-time
edited_at
required

Null until the message is edited.

string | null format: date-time
Example
{
  "data": {
    "type": "standard",
    "author": {
      "type": "human"
    }
  }
}

401

Section titled “401”

The token is missing, malformed, or revoked.

Media typeapplication/json

The shape every error response carries.

object
message
required
string
Examplegenerated
{
  "message": "example"
}

403

Section titled “403”

The token lacks the scope this operation requires, or its subject may see the resource but not perform this action on it.

Media typeapplication/json

The shape every error response carries.

object
message
required
string
Examplegenerated
{
  "message": "example"
}

404

Section titled “404”

The resource does not exist, is outside the token’s workspace, or the integrations platform is disabled. A channel the subject cannot see is reported here rather than as a 403, so the API never leaks its existence.

Media typeapplication/json

The shape every error response carries.

object
message
required
string
Examplegenerated
{
  "message": "example"
}

422

Section titled “422”

The request body failed validation.

Media typeapplication/json
object
message
required
string
errors
required

The failing fields, each mapped to its messages.

object
key
additional properties
Array<string>
Examplegenerated
{
  "message": "example",
  "errors": {
    "additionalProperty": [
      "example"
    ]
  }
}

429

Section titled “429”

The per-token rate limit (INTEGRATIONS_API_RATE_LIMIT requests per minute) was exceeded. Retry after the Retry-After header.

Media typeapplication/json

The shape every error response carries.

object
message
required
string
Examplegenerated
{
  "message": "example"
}

Headers

Section titled “Headers”
Retry-After
integer

Seconds to wait before retrying.