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. Button to see poll result

    Really often, people on Twitter define a choice on their poll just to let people not concerned see the result. Why not providing a simple button to let anybody see the result without having to choose an answer ?

    5 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

    acknowledged  ·  0 comments  ·  General features  ·  Flag idea as inappropriate…  ·  Admin →
  2. Use cases for the ability to limit who can reply to a Tweet in the API

    The API should support limiting who can reply to a Tweet when Tweeting using POST statuses/update. This could be useful for publishing tools that can be used to schedule and publish Tweets across different accounts (e.g. a brand account in multiple languages).

    What are other use cases where you would want to limit who can reply to a Tweet through the API?

    5 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  ·  Tweet Reply Settings Experiment  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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…

    5 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

    2 comments  ·  Filtered stream  ·  Flag idea as inappropriate…  ·  Admin →
  4. 4 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  ·  Documentation and resources  ·  Flag idea as inappropriate…  ·  Admin →
  5. Date of last activity in Get labs/2/users expansions

    It's useful to have the date of last activity of a user. Before we could deduce it from the most recent tweet but now it's gone in v2 and it become really tricky to get this information.

    4 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

    acknowledged  ·  0 comments  ·  GET users  ·  Flag idea as inappropriate…  ·  Admin →
  6. GraphQL

    While I understand the motivation for the separate "expansions" in the GET Tweets endpoint, I wonder if you have considered using GraphQL to allow the user to determine the shape of the tweet data returned?

    In adding support for the labs endpoint to twarc [1] I found that I wanted to knit back together the data that is separated out into tweets. If GraphQL was used I don't think this would be necessary.

    I would be curious to know if Twitter Labs considered switching to GraphQL for fetching tweets and users.

    [1] https://github.com/docnow/twarc

    4 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

    acknowledged  ·  0 comments  ·  GET Tweets  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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…

    4 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

    closed  ·  1 comment  ·  General features  ·  Flag idea as inappropriate…  ·  Admin →
  8. Add an option to forward a tweet

    To enable one to send a tweet to a group

    4 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

    acknowledged  ·  2 comments  ·  General features  ·  Flag idea as inappropriate…  ·  Admin →
  9. Tweet translation should be available through the API

    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.

    4 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

    acknowledged  ·  1 comment  ·  General features  ·  Flag idea as inappropriate…  ·  Admin →
  10. Bring Back Search Type Popular On Recent Search

    Hello, in previcious versions we used to filter with all tweets by popular recent and mixed . Now it is gone. Can you please bring it back

    3 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  ·  Recent search  ·  Flag idea as inappropriate…  ·  Admin →
  11. Support non-public metrics via OAuth 2.0 for the Labs v2 'Tweets and Users' endpoint

    With API v2 (Labs v2) launching last week, it seems incredible that some endpoints still require the use of oAuth 1.0 which is scarcely supported. This makes developing for the 'next gen' API feel surprisingly primitive - and is an accessibility barrier that is unique in the sophisticated landscape of 2020.

    3 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  ·  General features  ·  Flag idea as inappropriate…  ·  Admin →
  12. Release from 3 day limit alert

    Giving us an alert when we are off our 3 day limit, because you guys give us one when we’re put on it but not when released from it.

    3 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

    2 comments  ·  General features  ·  Flag idea as inappropriate…  ·  Admin →
  13. World Hot Trends

    I suggest you to add hot trends.. Which has highest tweets in the world beside country trends it just suggestion named World hot trend... I feel it will get more contacts between people over world

    3 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  ·  General features  ·  Flag idea as inappropriate…  ·  Admin →
  14. Metric that indicates how many users have saved your tweet as a bookmark

    I think this metric is a unique way to gauge long-term engagement among users. Retweets can be likened to quick, instinctive reactions to content, but I think there is value in also providing users with measures that indicate more deliberative reactions (a good way to delineate these user behaviours can be best explained through 'System 1' vs 'System 2' thinking).

    For instance, suppose a professor tweets about a recently published academic paper. Whilst retweets provide insight into timely reactions, the academic might want to also keep track of other users who might potentially revisit/avail of their published content in the…

    3 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  ·  Tweet Metrics  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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
    3 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

    closed  ·  1 comment  ·  Sampled stream  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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

    3 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

    closed  ·  2 comments  ·  Filtered stream  ·  Flag idea as inappropriate…  ·  Admin →
  17. Wildcards in filtered stream

    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.

    3 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

    acknowledged  ·  1 comment  ·  Filtered stream  ·  Flag idea as inappropriate…  ·  Admin →
  18. First Tweet containing a hashtag

    Surface is the first tweet in the hashtag, to know the founder of the hashtag, it is his right; and also there are those who use the hashtag for no purpose intended for topic of the hashtag (no objection to it), but you are tired to reach the news for which the hashtag was founded due to the large number of tweets outside the same topic.

    3 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

    2 comments  ·  General features  ·  Flag idea as inappropriate…  ·  Admin →
  19. Add support for "sample" operator

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

    3 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

    acknowledged  ·  0 comments  ·  Recent search  ·  Flag idea as inappropriate…  ·  Admin →
  20. Hide Replies and Block Users should be combined in a wiser way

    Currently, there is an easy way troll farms already circumvent the "hide replies" feature:
    1) post a disinfo/harrassmt reply to a target account
    2) then immediately block (blacklist) the target account
    3) now the abusing reply is visible for everyone, but neither attacked account nor anyone else can do anything with it.

    I don't have a solution that will surely fix this. I understand that this is actually feedback on how Hide Replies works for users, not how it should be available via API. Any better place to post feedback on user feature and to be sure it will be

    3 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  ·  Hide replies  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Daniele responded

    Thank you for this feedback, and appreciate the level of detail. Your voice is heard here – We’re passing this to the team working on Hide replies for users so they can review.

  • Don't see your idea?

Feedback and Knowledge Base