With API v2 (Labs v2) launching last week, it seems incredible that some endpoints still require the use of oAuth 1.0 which is scarcely supported. This makes developing for the 'next gen' API feel surprisingly primitive - and is an accessibility barrier that is unique in the sophisticated landscape of 2020.3 votes
Create endpoint for get "quote tweets" by other to Tweets authored by the user. Like endpoint statuses/retweetsofme.14 votes
Note that you can now filter quote Tweets with Filtered stream in Labs using the `is:quote` operator: https://developer.twitter.com/en/docs/labs/filtered-stream/operators
Combined with other operators, this is a first step towards what you are describing.
Having access to an API for Twitter native polls would enable developers to create and schedule polls, as well as get back engagement data such as impressions, responses, Retweets of the poll, and their resulting responses, reach, and total engagement.40 votes
Some poll information has now been made available in Labs: https://developer.twitter.com/en/docs/labs/overview/whats-new/expansions
Hiding replies would be of massive value to our clients, but with the current rate limits, we wouldn't be able to meet their requirements.
Please can you provide forecasts as to when rate limits will be increased and what they will be increased to? Would this happen once the capability goes from Labs into live service?
Many thanks.1 vote
We are actively looking into a new rate limiting configuration to better serve production use case. We will update this idea as soon as we make progress.
Language consistency would be helpful.
API Representation uses "favorites", but the current Twitter interface uses "likes".
In the documentation for "Account Activity API" notes "likes", while in "Search Tweets" notes as "favorites".
Perhaps not all of us are aware that "favorites" is a precedent of "likes".
Twitter could include a list of approved Twitter libraries for different programming languages in the documentation. This would equip developers with robust resources and help them know which resources they can rely on to use the Twitter API.9 votes
Twitter could build a more affordable version of the enterprise Engagement API, which would provide developers with Tweet metrics for owned Tweets.
Engagement data returned by the API includes number of Likes, Retweets, replies, impressions, and engagements (for example, number of link clicks). This API would enable developers to better understand their reach and impact on Twitter.11 votes
There can be a huge upfront effort to sift through the volume of Tweet data in order to get a data set that is interesting and valuable. It would be great to add more upfront filtering options to reduce the amount of data needed for statistically relevant analysis.6 votes
- Don't see your idea?