"page does not exist" with direct_messages/destroy?


Does Twitter turn off the https://api.twitter.com/1.1/direct_messages/destroy.json?

I constantly get page does not exist meesage after I send out the request.


I’m not seeing any issues with deleting direct messages by ID. Are you sure that the ID you’re specifying belongs to a direct message that exists? Make sure you’re using id_str to retrieve the identifiers, as our direct message IDs can go to 64-bit, which munges the integer in some languages.