Twitter Developer Feedback

Twitter API

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Filtered Stream limits after Early Access

    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.

    41 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Tweets: Filter Stream  ·  Flag idea as inappropriate…  ·  Admin →
  2. Tweets not returning when user is tagged in Image

    We have observed that we get the tagged information of the users if they are tagged in the text portion of the tweet. However when a user is being tagged in the image we do not get any information about that.
    Can we add these features in next release.

    20 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Tweets: Filter Stream  ·  Flag idea as inappropriate…  ·  Admin →
  3. Allow wildcards in filter stream queries

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

    Use-cases:

    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
    16 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Tweets: Filter Stream  ·  Flag idea as inappropriate…  ·  Admin →
  4. Exclude a large number of users from filtered stream/search results

    With the strict monthly limit on how many tweets you can get from searches or streams, it's important to be able to pare down the returned results as much as possible. As it stands now, it is possible for a malicious user to create many Twitter accounts and spam tweets that intentionally use up an application's monthly quota. It's possible to exclude some users by adding to the search query or filtered stream rule, but once the character limit is hit, no further recourse is possible.

    Various ideas to combat this:
    - Ability to exclude muted/blocked users from appearing in…

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Tweets: Filter Stream  ·  Flag idea as inappropriate…  ·  Admin →
  5. stream

    There is no way to know what connections are still on. I keep getting 429 errors. I just restarted my backend for some refactoring and now I can't connect anymore. Wish I could see a list and revoke dangling connections, if there are any

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Tweets: Filter Stream  ·  Flag idea as inappropriate…  ·  Admin →
  6. filter

    filter stream

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Tweets: Filter Stream  ·  Flag idea as inappropriate…  ·  Admin →
  7. V2: Describe which rules failed to delete

    When deleting multiple rules in the V2 Filtered Streams Rules API, if some rules fail to delete the response object does not state which rules failed and which rules succeeded.

    Example Response

    {"meta":{"sent":"2021-02-03T18:07:46.343Z","summary":{"deleted":1,"not_deleted":3}},"errors":[{"errors":[{"parameters":{},"message":"Rule does not exist"}],"title":"Invalid Request","detail":"One or more parameters to your request was invalid.","type":"https://api.twitter.com/2/problems/invalid-request"},{"errors":[{"parameters":{},"message":"Rule does not exist"}],"title":"Invalid Request","detail":"One or more parameters to your request was invalid.","type":"https://api.twitter.com/2/problems/invalid-request"},{"errors":[{"parameters":{},"message":"Rule does not exist"}],"title":"Invalid Request","detail":"One or more parameters to your request was invalid.","type":"https://api.twitter.com/2/problems/invalid-request"}]}

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Tweets: Filter Stream  ·  Flag idea as inappropriate…  ·  Admin →
  8. Allow larger queries in filter stream

    Allow queries of up to 4096 characters or more in the filter stream

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Tweets: Filter Stream  ·  Flag idea as inappropriate…  ·  Admin →
  9. We need location in order to migrate from 'statuses/filter' !

    We need location in order to migrate from v1 statuses/filter !

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Tweets: Filter Stream  ·  Flag idea as inappropriate…  ·  Admin →
  10. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Tweets: Filter Stream  ·  Flag idea as inappropriate…  ·  Admin →
  11. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Tweets: Filter Stream  ·  Flag idea as inappropriate…  ·  Admin →
  12. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Tweets: Filter Stream  ·  Flag idea as inappropriate…  ·  Admin →
  13. from:id1 OR from:id2 OR .... => from:id1,id2,..

    to track tweets from several users, the filter current format is:
    "from:id1 OR from:id2 OR ...."

    Would it be possible to have a coma seperated format like:

    "from:id1,id2,.. "

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Tweets: Filter Stream  ·  Flag idea as inappropriate…  ·  Admin →
  14. from:id1 OR from:id2 OR .... => from:id1,id2,..

    to track tweets from several users, the filter current format is:
    "from:id1 OR from:id2 OR ...."

    Would it be possible to have a coma seperated format like:

    "from:id1,id2,.. "

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Tweets: Filter Stream  ·  Flag idea as inappropriate…  ·  Admin →
  15. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Tweets: Filter Stream  ·  Flag idea as inappropriate…  ·  Admin →
  16. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Tweets: Filter Stream  ·  Flag idea as inappropriate…  ·  Admin →
  17. Add proximity and NEAR operators in filter stream queries

    PowerTrack has a proximity operator (~), documented like this:

    Commonly referred to as a proximity operator, this matches an activity where the keywords are no more than N tokens from each other. If the keywords are in the opposite order, they can not be more than N-2 tokens from each other. Can have any number of keywords in quotes. N cannot be greater than 6.

    This operator is very useful, and it would be great to have it in filter stream queries.

    Additionally, it would be great to have a NEAR operator, with the same use-cases as ~, but for…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Tweets: Filter Stream  ·  Flag idea as inappropriate…  ·  Admin →
  18. Add a country operator in filter stream queries, like PowerTrack's geo enrichment

    Being able to filter by users' location/country is very useful (this is something that exists in PowerTrack, but not yet in API v2)

    Use-case:

    International businesses that want to monitor only one of the countries they operate in, or that want to route mentions from different countries to different offices. This is also very useful in reporting.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Tweets: Filter Stream  ·  Flag idea as inappropriate…  ·  Admin →
  19. Merhaba, Twitter hesabım askıya alındı. Farkında olmadan Twitter kurallarını ihlal ettim. Bu durumdan dolayı özür dilerim. Twitter hesabım

    Merhaba,

    Twitter hesabım askıya alındı. Farkında olmadan Twitter kurallarını ihlal ettim.

    Bu durumdan dolayı özür dilerim. Twitter hesabım açıldıktan sonra kurallara uyacağım ve bir daha böyle bir hata yapmayacağım.

    Sizden hesabımın tekrar açılmasını rica ediyorum.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Tweets: Filter Stream  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base