Dm channels

Retrieve dm channel

Retrieves the details of an existing DM channel.

Required permissions (one of):

  • dms:read
  • support_chat:read
get/dm_channels/{id}

Path parameters

idstring required

The unique identifier of the DM channel to retrieve.

Response

A successful response

created_atstring required

The time the entity was created (in milliseconds since Unix epoch)

idstring required

The unique identifier for the entity

last_message_atstring date-time nullable required

The timestamp when the most recent message was sent in this channel. Null if no messages have been sent.

namestring nullable required

A custom display name assigned to this channel by the user. Null if no custom name has been set.

Example response

{
  "created_at": "123.45",
  "last_message_at": "2023-12-01T05:00:00.401Z",
  "name": "Project Alpha Team"
}

Changes

Changed in 50 of the 74 revisions of this API.100

    • ○

      the security scope dms:read was added to the endpoint's security scheme bearerAuth

      api-security-scope-added

    • ○

      the security scope support_chat:read was removed from the endpoint's security scheme bearerAuth

      api-security-scope-removed

    • ○

      the security scope dms:read was added to the endpoint's security scheme bearerAuth

      api-security-scope-added

    • ○

      the security scope support_chat:read was removed from the endpoint's security scheme bearerAuth

      api-security-scope-removed

    • ○

      the security scope dms:read was added to the endpoint's security scheme bearerAuth

      api-security-scope-added

    • ○

      the security scope support_chat:read was removed from the endpoint's security scheme bearerAuth

      api-security-scope-removed

    • ○

      the security scope dms:read was added to the endpoint's security scheme bearerAuth

      api-security-scope-added

    • ○

      the security scope support_chat:read was removed from the endpoint's security scheme bearerAuth

      api-security-scope-removed

    • ○

      the security scope dms:read was added to the endpoint's security scheme bearerAuth

      api-security-scope-added

    • ○

      the security scope support_chat:read was removed from the endpoint's security scheme bearerAuth

      api-security-scope-removed

    This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

    • ○

      the security scope dms:read was added to the endpoint's security scheme bearerAuth

      api-security-scope-added

    • ○

      the security scope support_chat:read was removed from the endpoint's security scheme bearerAuth

      api-security-scope-removed

    • ○

      the security scope dms:read was added to the endpoint's security scheme bearerAuth

      api-security-scope-added

    • ○

      the security scope support_chat:read was removed from the endpoint's security scheme bearerAuth

      api-security-scope-removed

    This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

    • ○

      the security scope dms:read was added to the endpoint's security scheme bearerAuth

      api-security-scope-added

    • ○

      the security scope support_chat:read was removed from the endpoint's security scheme bearerAuth

      api-security-scope-removed

    • ○

      the security scope dms:read was added to the endpoint's security scheme bearerAuth

      api-security-scope-added

    • ○

      the security scope support_chat:read was removed from the endpoint's security scheme bearerAuth

      api-security-scope-removed

    • ○

      the security scope dms:read was added to the endpoint's security scheme bearerAuth

      api-security-scope-added

    • ○

      the security scope support_chat:read was removed from the endpoint's security scheme bearerAuth

      api-security-scope-removed

Of the 74 revisions, 1 has no diff computed.