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

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

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

    38 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 →
  4. 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 →
  5. 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 →
  6. 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".

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

    acknowledged  ·  3 comments  ·  GET Tweets  ·  Flag idea as inappropriate…  ·  Admin →
  8. Build an API to manage polls and poll results

    Having access to an API for Twitter native polls would enable developers to create and schedule polls, as well as get back engagement data such as impressions, responses, Retweets of the poll, and their resulting responses, reach, and total engagement.

    22 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 →
  9. 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 →
  10. Provide developers with an API testing console

    As a new developer, I want a lightweight way to make an API call within the documentation with little setup involved. I need to see and evaluate quickly what a request and response looks like for a specific endpoint.

    14 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  ·  Documentation and resources  ·  Flag idea as inappropriate…  ·  Admin →
  11. Consistency for "Likes" and "Favorites"

    Language consistency would be helpful.


    • API Representation uses "favorites", but the current Twitter interface uses "likes".


    • In the documentation for "Account Activity API" notes "likes", while in "Search Tweets" notes as "favorites".


    • Perhaps not all of us are aware that "favorites" is a precedent of "likes".


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

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

    9 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 →
  15. Build a more accessible version of the engagement metrics API

    Twitter could build a more affordable version of the enterprise Engagement API, which would provide developers with Tweet metrics for owned Tweets.

    Engagement data returned by the API includes number of Likes, Retweets, replies, impressions, and engagements (for example, number of link clicks). This API would enable developers to better understand their reach and impact on Twitter.

    9 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  ·  General features  ·  Flag idea as inappropriate…  ·  Admin →
  16. Recommend and endorse a good Twitter library

    Twitter could include a list of approved Twitter libraries for different programming languages in the documentation. This would equip developers with robust resources and help them know which resources they can rely on to use the Twitter API.

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

    We’ll send you updates on this idea

    acknowledged  ·  6 comments  ·  Documentation and resources  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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 →
  18. 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 →
  19. 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 →
  20. 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).

    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  ·  Filtered stream  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for the feedback. This is not on our roadmap for the near-term future. However, we understand the problem that you are facing and we will bear this in mind going forward.

← Previous 1 3 4
  • Don't see your idea?

Feedback and Knowledge Base