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. Include Reach in metrics API

    Include message lifetime reach (unique impressions) and profile-level daily reach metrics for messages. This provides better insight into the number of individuals that saw a specific tweet or content associated with a profile/brand.

    6 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  ·  Tweet Metrics  ·  Flag idea as inappropriate…  ·  Admin →
  2. labs/1/tweets and Get labs/1/users rate limits

    It appears that the user-auth rate limits in the labs API is shared among all users.
    I could see however that app-auth limits are separate, so there is distinction between app-auth vs user-auth, just not working as expected

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

    We’ll send you updates on this idea

    started  ·  2 comments  ·  GET Tweets  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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 →
  4. Add premium endpoints for the following/followers endpoints

    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!

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

    We’ll send you updates on this idea

    planned  ·  2 comments  ·  General features  ·  Flag idea as inappropriate…  ·  Admin →
  5. Help developers filter out spam or other noisy content

    There can be a huge upfront effort to sift through the volume of Tweet data in order to get a data set that is interesting and valuable. It would be great to add more upfront filtering options to reduce the amount of data needed for statistically relevant analysis.

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

    We’ll send you updates on this idea

    started  ·  1 comment  ·  Tweet Annotations  ·  Flag idea as inappropriate…  ·  Admin →
  6. Provide developers with an app usage tracking tool

    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.

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

    We’ll send you updates on this idea

    1 comment  ·  Documentation and resources  ·  Flag idea as inappropriate…  ·  Admin →
  7. API endpoint for getting bookmarks

    Get all bookmarked tweets by me

    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  ·  GET Tweets  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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 →
  9. 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 →
  10. 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 →
  11. 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 →
  12. Accept or deny follower requests (when tweets are protected)

    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

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

    We’ll send you updates on this idea

    acknowledged  ·  3 comments  ·  General features  ·  Flag idea as inappropriate…  ·  Admin →
  13. Add premium detailed engagement metrics end point

    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

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

    We’ll send you updates on this idea

    planned  ·  3 comments  ·  Tweet Metrics  ·  Flag idea as inappropriate…  ·  Admin →
  14. Access to Image Crop Information

    Is there any plan to allow access to the cropping rectangles that are associated with each media image? These are called focusrects and are nested under the originalinfo property of extended_entities.media and could be passed along with the rest of the media info in the API request.

    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  ·  GET Tweets  ·  Flag idea as inappropriate…  ·  Admin →
  15. "Followers you know" in Get labs/2/users expansions

    In the app or on the web, we can access to the list of "Followers you know" of another user. It could be nice to have this information in expansions too.

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

    We’ll send you updates on this idea

    1 comment  ·  GET users  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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
    Sign in
    (thinking…)
    Sign in with: Okta Twitter
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

  18. 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 →
  19. 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 →
  20. Allow API access to tweet analytics CSVs

    Specifically, some kind of way to download the csvs produced by exporting https://analytics.twitter.com/user/[INSERT DATA]/tweets given OAuth read (or even read/write) scope would be really useful

    3 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 →
  • Don't see your idea?

Feedback and Knowledge Base