Tips & Best Practices

  • In the existing API (POST direct_messages/new) we accept both user id and user screen name for recipient_id query parameter. For POST direct_messages/events/new (message_create), we will only be accepting i64 user id for “recipient_id”.
  • The entities objects will always be returned in the DM json, even if empty. This differs from the current DM API.
  • Direct Messages sent via POST direct_messages/events/new (message_create) will be accessible via the legacy Direct Message REST API. However, Quick Reply metadata will not be accessible via any legacy Direct Message REST API or Streaming API endpoints. Media attachments (images, videos, gifs) will continue to be available as entities in the legacy REST API.
  • Welcome Messages should not contain private data. All Welcome Messages that you configure using the APIs may be publicly accessible - even if you do not send them to a specific user. Anyone with the link to media shared in a Welcome Message will be able to view the content.
  • Default Welcome Messages can be set through the API by other third-party apps. In order to avoid conflicts, when allowing customers to change their default Welcome Message from within your solution, make sure you retrieve the current Welcome Message to display to them.