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.

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

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?

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.

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.

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.

Add more trending stations/places, like for north Indians its only Delhi.

To enable one to send a tweet to a group

At www.contexto.io and www.graphext.com we provide our customers the possibility of mapping and expanding Twitter communities leveraging the social graph. This allows us to get really contextual, relevant and different insights that most social media analytics tools offer (they mostly count keywords that matches a boolean query).

We currently use the free API following/followers endpoints for this right now but with the new policy starting this month we cannot make more than 100K requests/day which prevent us from scaling our product. We would be very happy to pay for a premium endpoint like this!

I would like the Twitter API to use OAuth 2.0 instead of OAuth 1.0. OAuth1.0a is fairly specific to the Twitter APIs at this point in time. It's complicated to implement, and there is a dwindling number of developer tools that support it. OAuth 2.0 is less complicated and easier to build into an app than OAuth 1.0.

Specifically, some kind of way to download the csvs produced by exporting https://analytics.twitter.com/user/[INSERT DATA]/tweets given OAuth read (or even read/write) scope would be really useful

If you are using a native Twitter app such as the Twitter app on Android, if you click on a link to a website, which uses "sign in with twitter" to authenticate the user, the user is forced to login again, even though they are already authenticated with Twitter in the native app.

In a perfect world this secondary sign in would not be necessary, and would reduce a lot of friction.

Build a new request operator that can be included in an API request, and returns a translation of the Tweet text in the Tweet payload. Supported languages should be the same languages that are supported by the "lang:" request operator.

Describe the level commitment (and dedication) to APIs.

What are the thresholds for usage & overall sunsetting of service?

What criteria will be used to make significant changes?