Tweet threads have become increasingly popular over the past few years. This API would enable developers to tap into the potential of threads by programmatically creating threads, as well as retrieving all Tweets in a thread.

I would like to recommend building a conversations API that enables developers to track updates to full conversation threads. This API would retrieve the entire conversation that a Tweet is in, and return all Tweets and replies within a given thread. This API would enable developers to go from a Tweet of interest to all replies in the thread, without having to recursively search for Tweets with the correct "inreplytostatusid".

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.

It would be really helpful to have an analytics endpoint in which the entity was a media ID (in my case a video ID) and you could request engagement & video metrics aggregated at the video level, even if that video appeared across many different tweets. Right now this is possible through the Engagement API for video views only, but it would be great if it were available through the Ads API & included seconds/minutes viewed, percentile completions, call to action clicks, etc.

It would be useful to be able to retrieve more than 100 results calling GET statuses/retweeters/ids
The current limitation doesn't make sense.

It will be really useful to be able to accept/deny follower requests with Twitter API when tweets are protected.
This feature exists but currently this is not public.

When I try to call this endpoint :

POST https://api.twitter.com/1.1/friendships/accept.json?user_id=<follower id>

I've received : {"errors":[{"code":37,"message":"Not authorized to use this endpoint."}]} - HTTP Code : 403

As a new developer, I want a lightweight way to make an API call within the documentation with little setup involved. I need to see and evaluate quickly what a request and response looks like for a specific endpoint.

Create endpoint for get "quote tweets" by other to Tweets authored by the user. Like endpoint statuses/retweetsofme.

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".

Why don't we have the same kind of statuses/retweeters/ids endpoint but for likes, in order to get all the user ids who liked a particular tweet ?

When I try to hide a Tweet in a thread that wasn’t started by the authenticating user, I get the response:

(
[title] => Forbidden
[type] => about:blank
[status] => 403
[detail] => Forbidden
)

I understand that this action should actually be forbidden, but the error in the API response doesn't tell me why the action is forbidden (which is that the authenticating user is trying to hide a Tweet in a thread that wasn't started by the authenticating user)

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.

We need a way to manage muted keywords, similar to the existing endpoints for muted users:

GET mutes/keywords/list
POST mutes/keywords/create
POST mutes/keywords/destroy

Add a field to know when media is being withheld by country

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.

In the app or on the web, we can access to the list of "Followers you know" of another user. It could be nice to have this information in expansions too.

The Tweet payload should contain a field that indicates whether a Tweet has been hidden. This can help people maintain display consistency regardless of where they manage their Twitter accounts. Researchers can find the field useful to understand circumstances such as relevancy, confusion and abuse.