New Fleets feature should be added to API documentation.

Users were able to download their archives for years (https://help.twitter.com/en/managing-your-account/how-to-download-your-twitter-archive), but this feature was disabled after the Twitter security incident in July.

Users now get the messages: "The download your data feature is unavailable right now. Try again at a later date."

Please re-enable this feature again as it's extremely useful for many users to access their account history and clean up their accounts.

The current limit for filtered stream is very small compared to the v1.1 API and we have no idea on the paid option to have increased limits on rules, characters per rule and total tweets. Is hard to plan ahead some features with the current information.
Can you provide the information on paid tiers of that endpoint? It's a big change to leave us without knowing is it even possible to pay for enough limit.

Change the keyword operator such that * matches one or more of any character.

Use-cases:

• Match a family of products with a common prefix




• Match part of compound words in dutch, finish, or german languages (among others) : https://en.wikipedia.org/wiki/Compound(linguistics)#Examplesfromdifferentlanguages )

Additionally, the character ? could behave like *, except that it would match exactly 1 character.

Limitations:

• Wildcard keywords could be a non-standalone operator


• A leading * or ? could be forbidden


• A non-trailing * or ? could be forbidden

User lookup returns fields like "protected", "withheld" and "verified" but there are no fields for suspended, restricted and deleted accounts.

can you please increase the rules limit?
currently in early access limit is 25
i want to use from: userid/username from 5k , 10k twitter handles.
each rule has char limit of 512, with such 25 rules/app and 512 chars/rule limits we will only be able to receive tweets from around 250~300 handles.

Just like the API to fetch all the retweets of a tweet.

Being able to search by minimum number of favourites and retweets as we could in API 1.1 would be great to see in Recent search API 2. This is particularly useful for a large volume of tweets, and being able to find the tweets with the most engagements.

If you request promoted metrics on a non-promoted tweet,it fails the entire request. Why not just return nulls or errors for those fields? No need to kill the whole tweet.

Applies to recent search too

Get all bookmarked tweets by me

Right now i can create only one project. Would be nice to have more projects possible per developer team.

Will there be any ability to do 3rd party authentication with Oauth 2.0, or will it remain in Oauth 1.0a?

Currently url is returned on images only.

When displaying a tweet it is import to show if the it has a "public-interest exception". Tweet objects that are returned by Version 2 endpoints should have a field that specifies the exception if one is present. I work for a major US news organization, so that is the context for my request.

I am getting error in response If I am sending not promoted tweet Id with the tweet fields promotedmetrics key with other fields like organicmetrics.

Instead of error in response, we can have a partial response ( in this case organic_metrics data ) with error is in another node.

The variants data is missing, making videos impossible to play inline.

The embeddable field is also missing, this is used to indicate that the photo media is actually a video that can only be played in a web browser.

extalttext is missing.