Go to Slack
DocumentationTutorialsTwitter

message.im event

A message was posted in a direct message channel

Compatibility: Events API

Expected scopes:
im:history  

This example appears wrapped in the standard event wrapper used by all events delivered on the Events API.

{
    "token": "one-long-verification-token",
    "team_id": "T061EG9R6",
    "api_app_id": "A0PNCHHK2",
    "event": {
        "type": "message",
        "channel": "D024BE91L",
        "user": "U2147483697",
        "text": "Hello hello can you hear me?",
        "ts": "1355517523.000005",
        "event_ts": "1355517523.000005",
        "channel_type": "im"
    },
    "type": "event_callback",
    "authed_teams": [
        "T061EG9R6"
    ],
    "event_id": "Ev0PV52K21",
    "event_time": 1355517523
}

The semantics for this message event type are similar to the core message event sent through the RTM API. Messages often include many more fields than those shown above.

Differentiate direct messages from other message.* events by looking for the event's channel_type field set to "im".

Looking for messages in your workspace app's app home? Subscribe to message.app_home instead. Learn more.

Events API compatibility

Subscribe to this event via the Events API.

Events of this type will be wrapped in metadata when sent via the Events API.

Unavailable in the RTM API

This event type is compatible only with the Events API.

When using the RTM API, the Events API's message.channels, message.im, message.mpim, and message.groups event types are presented as simple message events instead.

Related Articles