Twitter DM API broke around August 30, 2018

direct-messages

#1

I have been using the DM API successfully since October 2017 every day. Now I go back and see my logs that it broke around August 30, 2018. I didn’t change my code or config since Oct 2017.

The response I’m seeing https://api.twitter.com/1.1/direct_messages/new.json endpoint is:

{"errors":[{"code":34,"message":"Sorry, that page does not exist."}]}

Here’s the request:

[deleted to protect privacy]

Then I head to the documentation (https://developer.twitter.com/en/docs/direct-messages/sending-and-receiving/api-reference/new-event) to see that the URL is changed to https://api.twitter.com/1.1/direct_messages/events/new.json with an additional /events/ segment in it.

Can someone explain why this change happened in a breaking way? Also what happened on August 30, 2018.?


#2

Hmm looks like there was some announcement at https://developer.twitter.com/en/docs/direct-messages/sending-and-receiving/guides/direct-message-migration which is not reachable anymore.

Found this link through:

I wish the announcement was still up. :frowning:


#3

The legacy DM API was deprecated and removed as was announced several times on the blog and in this community.

To continue interacting with Twitter direct messages you’ll need to switch to the new API.


#4

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.