Twitter Developer Feedback

Twitter Developer Labs

We want to hear your ideas for Twitter Developer Labs! How would you improve the current available endpoints in Labs, and what other things would you like us to consider building?

1. See what other ideas have been submitted and vote for ideas you like.
2. If you have an idea that isn't already listed, create a new post.
3. Include only one idea per post.

To start, we have added in a few ideas that have been suggested by developers in the past. Please vote or comment on those, if they reflect your own vision.

To share additional feedback about your experience with Labs, please take this short survey

Thank you for participating!

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Bookmark feature to improve organization

    Ability to categorize bookmarks and have a search bar included in that feature as well. This will permit users to access their favorite saved posts quicker and more efficiently. Organization is rooted in the most common reasons of dislike while utilizing social media applications, so with this tool you would be killing two birds with one stone. Simply by gaining attention from current and new users as well to compete with other applications while getting rid of this nuisance.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Okta Twitter
    Signed in as (Sign out)

    We’ll send you updates on this idea

    closed  ·  1 comment  ·  General features  ·  Flag idea as inappropriate…  ·  Admin →
  2. Change Filter Rules API, Lengths and Limits

    Currently 1 rule is limited to 512 characters, and there are 10 rules.

    The rules API would make more sense if there was a limit on operators and a number of them, rather than the character length of rules. For example: when using multiple follow:user or follow:id it can get unpredictable due to the varied length of screen_names and user IDs created before 64bit snowflake user ids.

    To make the rules API more useful, there should instead be a limit on the number of specified operators, not rules or rule character lengths.

    This way, i should be able to specify…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Okta Twitter
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Filtered stream  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for the feedback! We are aware of this ask, but we will not be making any changes to this in the near-future. As such, I am going to close this suggestion. However, please continue to vote for this idea if it resonates with you.

  3. Bug: incorrect like_count stats in the sample stream

    I got this json data out of https://api.twitter.com/labs/1/tweets/stream/sample?format=detailed

    This tweet https://twitter.com/theA1wife/status/1236899957858164736 has ~20K likes right now, though the stats in the json show 0 like_count.

    I apologize if this isn't where bugs go, but I didn't find anywhere else to post this.

    ```

    {
    
    "data": {
    "id": "1236899957858164736",
    "created_at": "2020-03-09T06:21:45.000Z",
    &quot;text&quot;: &quot;RT @JLo: Wait for it! @AROD <a rel="nofollow noreferrer" href="https://t.co/MNAxO0z2BA">https://t.co/MNAxO0z2BA</a> <a rel="nofollow noreferrer" href="https://t.co/PZIlDlTvyt&quot;">https://t.co/PZIlDlTvyt&quot;</a>,
    &quot;author_id&quot;: &quot;960338257190862849&quot;,
    &quot;referenced_tweets&quot;: [
    {
    &quot;type&quot;: &quot;retweeted&quot;,
    &quot;id&quot;: &quot;1236865771692670976&quot;
    }
    ],
    &quot;attachments&quot;: {
    &quot;media_keys&quot;: [
    &quot;7_1236865730156494848&quot;
    ]
    },
    &quot;entities&quot;: {
    &quot;urls&quot;: [
    {
    &quot;start&quot;: 28,
    &quot;end&quot;: 51,
    &quot;url&quot;: &quot;<a rel="nofollow noreferrer" href="https://t.co/MNAxO0z2BA&quot;">https://t.co/MNAxO0z2BA&quot;</a>,
    &quot;expanded_url&quot;: &quot;<a rel="nofollow
    2 votes
    Sign in
    (thinking…)
    Sign in with: Okta Twitter
    Signed in as (Sign out)

    We’ll send you updates on this idea

    closed  ·  1 comment  ·  Sampled stream  ·  Flag idea as inappropriate…  ·  Admin →
  4. Difference between the result of Twitter search screen and the return value of API

    In some cases, the result of a search set to include a specific word in the advanced search of twitter is slightly larger than the return value of the API. However, some tweets only appear in the return value of the API.
    Why is this? Why aren't they unified?

    This is the advanced search screen I am talking about.
    https://twitter.com/search-advanced?f=live

    We want the same result as searching for AAA in the advanced search screen, so the API rules are:
    "(AAA OR bio_name: AAA) -is: retweet"
    Please let me know if anything is wrong.

    Thank you

    2 votes
    Sign in
    (thinking…)
    Sign in with: Okta Twitter
    Signed in as (Sign out)

    We’ll send you updates on this idea

    closed  ·  2 comments  ·  Filtered stream  ·  Flag idea as inappropriate…  ·  Admin →
  5. Filters other than the rules I created

    The following is written on this page.
    "The stream leverages some of our content filtering technology where we exclude high-confidence noisy content."
    https://developer.twitter.com/en/docs/labs/filtered-stream/faq

    This is a different filter than the one I created.
    To make sure that my filters work properly, I need to turn off content filtering technology.
    I want to create an option that does not use content filtering technology.
    It is up to each user to get the data to determine which tweets are noisy.

    Thank you.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Okta Twitter
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Filtered stream  ·  Flag idea as inappropriate…  ·  Admin →
  6. Allow to access historical replies for a depth of a year for subscribed users

    As hiding criterias tend to change over time (eg global grey-list of unwanted commenters to hide), I wish my app would be able to retroactively access (and hide/unhide) historical replies to historical tweets of subscribed users with a depth of eg at least a year from now.

    At least, to access the list of replies my app had previously hidden.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Okta Twitter
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Hide replies  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for the feedback! This is not currently on our roadmap, but keeping track of the replies that have been hidden by your app should be fairly straightforward to do on your end. It would be helpful if you could give us additional insight into why this feature is important for you and tell us more about your use case.

  7. Filtered Stream monthly limits

    I read in this announcement https://twittercommunity.com/t/new-filtered-stream-endpoints-available-in-labs-and-the-future-of-statuses-filter/129888 that the new Filtered Stream endpoint, available in Labs, will be subject to monthly limits on the amount of tweets retrieved.
    Do you think that this kind of limitation will also be present in the version released in the future?

    I didn't find this kind of limitation on the old endpoint "statuses/filter".
    In this answer on stackoverflow https://stackoverflow.com/questions/34962677/twitter-streaming-api-limits
    , the idea of a limit on the endpoint "status/filter" based on the amount of tweets delivered within a certain percentage threshold compared to the totality of tweets generated on twitter was mentioned.
    I find that…

    3 votes
    Sign in
    (thinking…)
    Sign in with: Okta Twitter
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Filtered stream  ·  Flag idea as inappropriate…  ·  Admin →
  8. Add a filter to return only currently promoted tweets

    Currently there is no way to only return promoted tweets. With a "filter:promoted" filter option, it would be possible to only return promoted tweets combined with other search terms.

    This feature would help researchers and increase ad transparency.

    19 votes
    Sign in
    (thinking…)
    Sign in with: Okta Twitter
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  GET Tweets  ·  Flag idea as inappropriate…  ·  Admin →
  9. Filter tweets by users list

    It could be great to be able to use the "list:username/list-name" search parameter into the filtered stream endpoint, to watch tweets from a list of users rather than chaining "from:usernameX" parameters until the 10*512 chars are used.

    Especially since the new endpoint will replace the current one that currently allows to watch up to 5k users (the "from:xxx OR " method will only allow to watch 250 to 400 users depending on the average username length ; that's more than 10x less than before).

    7 votes
    Sign in
    (thinking…)
    Sign in with: Okta Twitter
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Filtered stream  ·  Flag idea as inappropriate…  ·  Admin →
  10. Richer Direct Messaging API to enable creating more powerful BOTs

    To enable a truly rich bot experience on Twitter, the API is missing things like:
    - Cards message type (image + text + buttons +swipe left/right)
    - Buttons and menus as part of message (not only Quick Replies)
    - A more integrated webview, that is an integral part of the bot experience (for example the bot sends a "pick your seat" button which opens a small size web widget right in the chat to pick the seat, and then goes back to the main chat bot flow)
    And most important:
    the fixed limit of 15k DM regardless of number of…

    3 votes
    Sign in
    (thinking…)
    Sign in with: Okta Twitter
    Signed in as (Sign out)

    We’ll send you updates on this idea

    closed  ·  1 comment  ·  General features  ·  Flag idea as inappropriate…  ·  Admin →
  11. Bypass "sign in with twitter" when using browser embedded in native Twitter app

    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.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Okta Twitter
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General features  ·  Flag idea as inappropriate…  ·  Admin →
  12. Twitter follow/unfollow Limits

    Hi, I'd love for twitter to readjust the current Follow/unfollow Limits currently set for each app.. we understand these limits are being set to eliminate spam activities on twitter but there should be an exclusion to this rule. for example there could be restrictions as to who can be followed or unfollowed (spammed) by the app/service and this should be limited to only those that use the same service/app reason being that the users already know what they're getting into. the funny thing is - users already know how to do these these without even using a 3rd party service.…

    3 votes
    Sign in
    (thinking…)
    Sign in with: Okta Twitter
    Signed in as (Sign out)

    We’ll send you updates on this idea

    closed  ·  1 comment  ·  General features  ·  Flag idea as inappropriate…  ·  Admin →
  13. Allow access to DM group conversations via Twitter API

    Currently we can access 1on1 DM via Twitter API but not group conversations. If we forcibly set the group's conversation_id, Twitter API returns forbidden. Allow this.
    ref
    https://developer.twitter.com/en/docs/direct-messages/sending-and-receiving/api-reference/new-event

    46 votes
    Sign in
    (thinking…)
    Sign in with: Okta Twitter
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  General features  ·  Flag idea as inappropriate…  ·  Admin →
  14. Fully adopt OAuth 2.0

    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.

    6 votes
    Sign in
    (thinking…)
    Sign in with: Okta Twitter
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  General features  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base