Are there any plans to include IDs of replies when returning a Tweet object?

replies

#1

I’m seeing posts from 2013 asking about the ability to retrieve replies, but it seems this feature is still unavailable. Is it too taxing on the database to include reply IDs, or is there another reason they’re not available? If reply IDs can’t be included in a Tweet object, could there at least be a way to retrieve replies in a separate Search request? I know you can already search for replies to a given user, but I’m looking for replies to a given Tweet.

This would be a powerful feature and enable the creation of very interesting applications. I hope this is under consideration, as I believe Twitter is an important platform and could benefit from making this data available to API consumers.


#2

Thanks for the suggestion. There are no current plans to add this to the API, but we are aware that it is not currently as easy as many people would like to build out conversation threads.


#3

Thanks for the reply. “Not currently as easy as many people would like” is a bit of an understatement… without reply data, it is literally impossible for me to retrieve a branched conversation. If I had the last tweet, I could work my way backwards to retrieve a single-threaded back-and-forth reply chain, but that doesn’t give us the full complexity of a branched conversation with potentially multiple replies to a given Tweet.

Maybe Twitter doesn’t see the value of working with complex conversations, or it wants to deny developers this ability because they want to save it for an in-house project. Either way, it’s frustrating for me and any other developer that wants to work with complex conversational data.


#4

I think that twitter conversations are like a treasure, but if it’s impossibile to have ID of replies to a tweet via API, it’s impossible to be able to exploit it.

I use tool like Treeverse, but it’s not the right tool to dive in twitter conversations.

Please enable the list replies ID, for every tweet ID.

Thank you


#5

In twitter now it’s impossible to discover the richness and the depth of a conversation.

Here two visualization of the same thread:


#6

Technically it is possible, just difficult and resource intensive:

There is an expensive way to get full conversations by recursively getting replies using in_reply_to_status_id in PowerTrack enterprise api, starting with the root tweet, and making requests for every reply up to some depth (or as long as there’s replies)

To do the same with the normal search API, you need to use to:screen_name then filter / reconstruct conversations based on ids yourself, then recursively do the same for every replying user down the thread, and up to some depth. This takes a lot of calls & tweets, even for relatively short conversations.

Even Twitter’s own web / mobile interfaces don’t load the full conversation threads.