Images in tweets should have their alt text available via API. Make it obvious. Here is where I would have expected to find it: https://developer.twitter.com/en/docs/tweets/data-dictionary/overview/entities-object#media

Currently there is no way to only return promoted tweets. With a "filter:promoted" filter option, it would be possible to only return promoted tweets combined with other search terms.

This feature would help researchers and increase ad transparency.

Currently we can access 1on1 DM via Twitter API but not group conversations. If we forcibly set the group's conversation_id, Twitter API returns forbidden. Allow this.
ref
https://developer.twitter.com/en/docs/direct-messages/sending-and-receiving/api-reference/new-event

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.

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

Get all bookmarked tweets by me

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.

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

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)

Wildcards would be very nice to have in filtered streams: Customers want them, and there is no way to emulate it on our side.

When a query term contains a * character, * would match any character in a tweet, one or more time. When a query term contains a ? character, ? would match any character, exactly one time.

For example, Tw*ter would match Twitter, Tweeter, Twiter, Tweetter.

It could be great to be able to use the "list:username/list-name" search parameter into the filtered stream endpoint, to watch tweets from a list of users rather than chaining "from:usernameX" parameters until the 10*512 chars are used.

Especially since the new endpoint will replace the current one that currently allows to watch up to 5k users (the "from:xxx OR " method will only allow to watch 250 to 400 users depending on the average username length ; that's more than 10x less than before).

The standard search API is somehow regarding screen name as part of text body and therefore is also searching in screen names. That can cause the search results to contain irrelevant tweets. For example, searching the word "nature" can return @human_nature's tweets whose text bodies don't contain the word "nature".

A similar issue applies to user mentions. For example, searching the word "nature" can return tweets which contain user mention @human_nature and don't contain the word "nature".

Please consider implementing an option which prevents the standard search API from searching in screen names and user mentions. Thanks.

Queries can only contain a limited number of terms and characters. It would be very useful to increase this llimit.

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

Surface is the first tweet in the hashtag, to know the founder of the hashtag, it is his right; and also there are those who use the hashtag for no purpose intended for topic of the hashtag (no objection to it), but you are tired to reach the news for which the hashtag was founded due to the large number of tweets outside the same topic.

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.