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

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

Extra Rules and Tweet allowance for Filtered Stream.

We have an integration with the Filtered Stream API and on-boarding some private beta customers.

I expect we'll exhaust the number of Rules and volume of Tweets with a handful of customers soon.

Idea: - option(s) to opt into extra Rules/volume of Tweets.

PAYG model would work or having a Premium Filtered Stream API offering please.

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!

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

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.

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 currently use the statuses/sample endpoint to stream 1% of Tweets and related compliance events for those Tweets. Having the deleted Tweet events helps me know when Tweets I've received are no longer available so that my database and application stay compliant with Twitter's policies.

Please give me a similar compatible and convenient way to keep the data received from Sampled stream compliant.

Twitter could include a tool in the developer portal that enables developers to monitor and manage usage across the different APIs, and helps them avoid unexpected rate limiting.

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?