So, when the recent search option appears the clear button is in the top right corner with the accounts aligning beneath. Being able to click which account you want to clear from your recent search history would be significant for those networking, attempting to save time from repetitive search, and users in general of course.

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.

Right now you can definitely get all the followers of a user, but I want to be able to sort those results by particular properties. So for example, I may want to sort my followers by the number of followers they have, in order to see my most "important" followers.

Developers may need to retrieve a list of hidden replies for a specific Tweet. This can be useful to obtain a list of Tweets can can be unhidden, given appropriate user consent. Developers can also create aggregate reporting via this API (for example, count how many Tweets are hidden per conversation, or per time period).

As we build the next generation of the Twitter API, we’re looking at how to rebuild the “follower graph” endpoints. Whether or not you’ve used the follow, search, and get users, or the mute, block and report users endpoints, we want to hear what you think. This is an effort to continue building in the open: sharing our roadmap and keeping you updated on our vision. As we have done in Twitter Developer Labs, this plan is not final, and with your feedback, will evolve over time.

Adding a trial or a demo developer account would be a great and fantastic idea because it well help the users to try something new and make them very interesting and in the other hand it well help twitter seeing their actions and knowing if they are able to be responsible of the developer account or not.

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

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

Please add an API endpoint for reporting accounts that are selling counterfeit digital goods. Hundreds of accounts are selling Netflix accounts, Spotify, and more. Just search "Netflix Premium Account" and see what I'm referring to. Why is this permitted? Can you please offer more through the API so we can help stop this?

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.

In the published standard search API, these parameters are in a single tweet object.

・User object

Screen_name and name are important elements in User Object.
Now we have to expand. This is very inconvenient.

Please add "name" and "screen_name" to the response data.

Support for the sample: operator. Many use cases would benefit from random samples. For example, sample:10 would return 10% across each hour...

It would be great if we can have another endpoint for metrics that would provide stats like the 28hr end point, so we can have more detailed metrics (link clicks, profile clicks etc) as well as hourly metrics

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.

I recently hit my monthly cap on the number of Tweets I consumed. I understand that this counter will reset on the day of the month I first enrolled for Labs. I can not find that date anywhere in the Labs UI. Please show me that date!

I was trying to summarize a conference in a moment with over 64 tweets. Trying to organize those manually moving them up and down 1-by-1 on the site was a pain (as many people tweet things not quite in chronological order of the conference or if you sorted once and want to add more later, it's hard).

It'd be great to expose the API for creating/editing moments so that other tools could help push the experience of capturing events or help to correlate topics and insert into proper places.

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.

Include message lifetime reach (unique impressions) and profile-level daily reach metrics for messages. This provides better insight into the number of individuals that saw a specific tweet or content associated with a profile/brand.