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. Build a conversation updates API

    I would like to recommend building a conversations API that enables developers to track updates to full conversation threads. This API would retrieve the entire conversation that a Tweet is in, and return all Tweets and replies within a given thread. This API would enable developers to go from a Tweet of interest to all replies in the thread, without having to recursively search for Tweets with the correct "inreplytostatusid".

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

    We’ll send you updates on this idea

    acknowledged  ·  5 comments  ·  General features  ·  Flag idea as inappropriate…  ·  Admin →
  2. Add an Endpoint for Aggregate Video Metrics Across Tweets

    It would be really helpful to have an analytics endpoint in which the entity was a media ID (in my case a video ID) and you could request engagement & video metrics aggregated at the video level, even if that video appeared across many different tweets. Right now this is possible through the Engagement API for video views only, but it would be great if it were available through the Ads API & included seconds/minutes viewed, percentile completions, call to action clicks, etc.

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

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

    We’ll send you updates on this idea

    5 comments  ·  GET Tweets  ·  Flag idea as inappropriate…  ·  Admin →
  4. Be able to get all the retweeters ids instead of the last 100 only

    It would be useful to be able to retrieve more than 100 results calling GET statuses/retweeters/ids
    The current limitation doesn't make sense.

    13 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 →
  5. API endpoint for getting bookmarks

    Get all bookmarked tweets by me

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

    We’ll send you updates on this idea

    acknowledged  ·  5 comments  ·  GET Tweets  ·  Flag idea as inappropriate…  ·  Admin →
  6. API response should contain descriptive error messages for actions that are forbidden

    When I try to hide a Tweet in a thread that wasn’t started by the authenticating user, I get the response:

    (
    [title] => Forbidden
    [type] => about:blank
    [status] => 403
    [detail] => Forbidden
    )

    I understand that this action should actually be forbidden, but the error in the API response doesn't tell me why the action is forbidden (which is that the authenticating user is trying to hide a Tweet in a thread that wasn't started by the authenticating user)

    8 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. Add a field to signal when media is being withheld by country

    Add a field to know when media is being withheld by country

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

    We’ll send you updates on this idea

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

    7 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 →
  9. GET statuses/likers/ids endpoint

    Why don't we have the same kind of statuses/retweeters/ids endpoint but for likes, in order to get all the user ids who liked a particular tweet ?

    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 →
  10. 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 →
  11. Add endpoints for muted keywords

    We need a way to manage muted keywords, similar to the existing endpoints for muted users:

    GET mutes/keywords/list
    POST mutes/keywords/create
    POST mutes/keywords/destroy

    5 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 →
  12. 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).

    5 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 →
  13. 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.

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

    5 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. 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.

    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 users  ·  Flag idea as inappropriate…  ·  Admin →
  16. Who to follow API

    Add an API version of the popular "Who to follow" link seen at lower right on the home page: https://twitter.com/<...>/whotofollow .
    (Currently it uses non-public APIs under the hood.)

    3 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  ·  GET users  ·  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
    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 →
  18. 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
    Sign in
    (thinking…)
    Sign in with: Okta Twitter
    Signed in as (Sign out)

    We’ll send you updates on this idea

    acknowledged  ·  0 comments  ·  Recent search  ·  Flag idea as inappropriate…  ·  Admin →
  19. Programmatically unhide a Tweet

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

    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  ·  Hide replies  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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 →
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base