Directmessage from update returns wrong response


When a direct message got placed using the special command “D” the api responds with the data of the last tweet instead of the just placed direct message.

My message has the following layout: “D @… test” and got delivered correctly, the api however responds like you’ve placed your latest status update. I’ve confirmed this result in my application with read/write access as well in the api console on They both got the wrong response.

Is anyone else having this problem? And is this a bug or normal behavior?


This is intentional – while you can write DMs to statuses/update using tweet commands, the documented response structure of that method is a tweet, so it returns the last tweet to satisfy that requirement about the response structure.

Use direct_messages/new for a more deterministic DM response.