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

    5 comments  ·  GET Tweets  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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 →
  3. API to report abuse/inappropriate content

    I suggest that the report features extend to API users. Report abuse is only available for individuals who get exposed to, click, and decide to report a tweet/account.

    A lot of inappropriate content is unfortunately on twitter. Perhaps I could categorize into 4 types:
    (1) inappropriate language: hate speech, harassment (bullying, sexual harassment)
    (2) inappropriate image: pornography, graphic violence
    (3) intention for inappropriate and harmful activities: intention to commit a crime (shooting, bomb, individual or mass threats), sell inappropriate products and services (prostitution, drugs - not debating if it is illegal or not, but I think twitter shouldn't be the…

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

    We’ll send you updates on this idea

    under review  ·  7 comments  ·  General features  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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)

    6 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 →
  5. Build an API to create and retrieve Tweet threads

    Tweet threads have become increasingly popular over the past few years. This API would enable developers to tap into the potential of threads by programmatically creating threads, as well as retrieving all Tweets in a thread.

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

    We’ll send you updates on this idea

    under review  ·  5 comments  ·  General features  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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

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

    44 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 →
  8. 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 →
  9. 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 →
  10. "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 →
  11. 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.)

    2 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 →
  12. Twitter should provide more granular app permissions

    Twitter currently offers three levels of app permissions: (1) read only; (2) read and write; (3) read, write and access Direct Messages. These options are not granular enough for some developers, and developers would like more options to choose from.

    For example, an app’s “write” permission could be segmented into more granular options: (1) write access to a user’s profile; (2) write access to a user’s network (follow/unfollow, mute, block, list modification); (3) write access to a user’s timeline, including the permission to Tweet, Retweet, or like a post.

    Another example includes Sign In With Twitter: there could be an…

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

    We’ll send you updates on this idea

    planned  ·  9 comments  ·  General features  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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".

    32 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 →
  14. 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.

    31 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 →
  15. 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

    1 vote
    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 →
  16. Make the endpoint rate limited at user level instead of app level

    We have built a social media management app that allows our customers to also view insights for their social accounts and posts.

    Every midnight we refresh insights for all posts published via our app in the past 7 days.

    For Twitter, we're only recording the number of favorites and retweets (returned by the /tweets endpoint), but we would like to gather more metrics, such as impressions, # of replies and video views.

    The current rate limit is 15 requests / 15 minutes and 50 Tweets / request.

    This basically means we can gather metrics for only 15 customers at a…

    11 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  ·  Tweet Metrics  ·  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. 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 →
  19. 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 →
  20. 1 vote
    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 →
← Previous 1 3 4
  • Don't see your idea?

Feedback and Knowledge Base