20 votesplanned · 4 comments · Twitter for Academic Research » APIs & Tools · Flag idea as inappropriate… · Admin →
An error occurred while saving the commentDigital Observatory Team commented
Main differences from the existing functionality:
- Higher rate limit enabled by much smaller payload. Why retrieve the raw JSON again for a tweet to check if it's live, when my only interest is the immutable field like tweet content?
Although the lookup API can do this (and a higher rate limit would ease this process), it's challenging to build a good pipeline around this. Most use cases of tweet data are going to require processing the raw JSON into some other more useful schema.
I don't see this as a replacement for statuses/lookup in terms of compliance, more an adjunct that allows a more rapid response and the ability to more frequently keep a collection in sync with live Twitter.Digital Observatory Team shared this idea ·
30 votesacknowledged · 2 comments · Twitter for Academic Research » General features · Flag idea as inappropriate… · Admin →
We are working on defining ways of retrieving a thread using a specific endpoint.
In the meantime, you can use the full archive search endpoint to retrieve an entire conversation thread (https://developer.twitter.com/en/docs/twitter-api/conversation-id).