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.

Thank you for participating!

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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.

  2. Allow to serve 10Ks-100Ks of users subscribed for a HideReplies app

    Allow a free-plan developer to serve 10Ks-100Ks of users subscribed for a "hide replies" allowing to hide tweets nearly real-time as they happen (provided that an app is capable to deal with such a firehose).

    This at least requires easy access to a stream of direct and indirect replies to the users subscribed.

    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 →
  3. 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
    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 →
    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.

  4. 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 →
  5. Need a way to manage compliance (deleted Tweets) while using Sampled stream

    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.

    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  ·  Sampled stream  ·  Flag idea as inappropriate…  ·  Admin →
  6. Programmatically unhide a Tweet

    Provide a way to programmatically unhide a previously hidden Tweet, given appropriate user consent.

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

    We’ll send you updates on this idea

    acknowledged  ·  0 comments  ·  Hide replies  ·  Flag idea as inappropriate…  ·  Admin →
  7. Show when a Tweet is hidden in the Tweet payload

    The Tweet payload should contain a field that indicates whether a Tweet has been hidden. This can help people maintain display consistency regardless of where they manage their Twitter accounts. Researchers can find the field useful to understand circumstances such as relevancy, confusion and abuse.

    4 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 →
  8. Retrieve a list of hidden replies to a given Tweet

    Developers may need to retrieve a list of hidden replies for a specific Tweet. This can be useful to obtain a list of Tweets can can be unhidden, given appropriate user consent. Developers can also create aggregate reporting via this API (for example, count how many Tweets are hidden per conversation, or per time period).

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

    We’ll send you updates on this idea

    acknowledged  ·  0 comments  ·  Hide replies  ·  Flag idea as inappropriate…  ·  Admin →
  9. Include "url_clicks" in Tweet Metrics endpoint

    We use the Engagement APIs extensively in our product. We currently have to use a combination of the /totals endpoint with the /28hour and /historical endpoints to get "urlclicks." Right now, the new Metrics labs endpoint provides all the great metrics that our customers want in a single endpoint except for "urlclicks."

    Without "urlclicks" it would be difficult to transition off of any of the Engagement APIs to a new Tweet Metrics endpoint. If this new endpoint had "urlclicks" we could replace all of our Engagement API usage pretty quickly and have better, more accurate data…

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

    We’ll send you updates on this idea

    planned  ·  0 comments  ·  Tweet Metrics  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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.

    17 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 →
  11. Create hackathons to empower young people

    Identify the needs for self-improvement that young people publish, segmenting them by themes, using sentiment analysis to quantify in percentage the positive perspective they have about it (the negative or neutral could also be deduced), thereby launching collaborative training programs with non-profit organizations

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

    We’ll send you updates on this idea

    acknowledged  ·  0 comments  ·  Documentation and resources  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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).

    6 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 →
  13. Optionally prevent the standard search API from searching in screen names and user mentions

    The standard search API is somehow regarding screen name as part of text body and therefore is also searching in screen names. That can cause the search results to contain irrelevant tweets. For example, searching the word "nature" can return @human_nature's tweets whose text bodies don't contain the word "nature".

    A similar issue applies to user mentions. For example, searching the word "nature" can return tweets which contain user mention @human_nature and don't contain the word "nature".

    Please consider implementing an option which prevents the standard search API from searching in screen names and user mentions. Thanks.

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

    We’ll send you updates on this idea

    acknowledged  ·  2 comments  ·  GET Tweets  ·  Flag idea as inappropriate…  ·  Admin →
  14. alt text via API

    Images in tweets should have their alt text available via API. Make it obvious. Here is where I would have expected to find it: https://developer.twitter.com/en/docs/tweets/data-dictionary/overview/entities-object#media

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

    We’ll send you updates on this idea

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

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

    We’ll send you updates on this idea

    acknowledged  ·  0 comments  ·  GET Tweets  ·  Flag idea as inappropriate…  ·  Admin →
  16. Add Moments API

    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.

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

    We’ll send you updates on this idea

    acknowledged  ·  1 comment  ·  General features  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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…

    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  ·  General features  ·  Flag idea as inappropriate…  ·  Admin →
  18. Add Endpoint to get retweet with comment aka 'Quote tweet'

    Create endpoint for get "quote tweets" by other to Tweets authored by the user. Like endpoint statuses/retweetsofme.

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

    We’ll send you updates on this idea

    6 comments  ·  General features  ·  Flag idea as inappropriate…  ·  Admin →
  19. Trending spots

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

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

    We’ll send you updates on this idea

    acknowledged  ·  2 comments  ·  General features  ·  Flag idea as inappropriate…  ·  Admin →
  20. Add an option to forward a tweet

    To enable one to send a tweet to a group

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

    We’ll send you updates on this idea

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

Feedback and Knowledge Base