Twitter Removes the 140 character limit from Direct Messages

June 11, 2015


Twitter has done a lot to improve Direct Messages over the past year and have much more exciting work on the horizon. One change coming in July that Twitter want to make you aware of now (and first!) is the removal of the 140 character limit in Direct Messages. In order to make this change as seamless as possible for you Twitter has included some recommendations below to ensure all your applications and services can handle these longer format messages before Twitter flips the switch.

Twitter recommends taking the following actions in preparation:

  1. Review the new API additions below.
  2. Update your GET requests so you will be able to receive the full length of DM text.
  3. Adjust your app UI to accommodate longer DM text.

Twitter encourages you to test and deploy the above changes in advance, but you won’t be able to send longer DMs until Twitter launches it in July. In the coming weeks though, Twitter will update this post to include directions on how to test these changes, as well as a more specific launch date.

You may be wondering what this means for the public side of Twitter. Nothing! Tweets will continue to be the 140 characters they are today.

Twitter's excited to hear your input. If you have technical questions, feel free to ask in the REST API forum or reach Twitter @TwitterDev. Thanks, and stay tuned for more!

API updates:

  • REST API
    DM read endpoints (GET direct_messagesGET direct_messages/sent and GET direct_messages/show)
    Send “full_text=true” as a query parameter to receive long DM text. If this parameter is not provided, you will get a truncated version of the DM. There will be no structural changes to the response returned by these endpoints.
    DM write endpoint (POST direct_messages/new)
    The “text” parameter will start accepting text longer than 140 characters. The new limit for DMs will be 10k characters.
  • Streaming API
    User Streams (GET user) and Site Streams (GET site) will automatically start receiving DMs that have text longer than 140 characters. Unlike the REST API, no additional parameter is needed. There will be no structural changes to the objects returned by these endpoints.


Adapted from a post on 11 June 2015 by Sachin Agarwal on the Twitter Community Blog.

Posted here with permission from Sachin Agarwal.