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

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

    We’ll send you updates on this idea

    4 comments  ·  General features  ·  Flag idea as inappropriate…  ·  Admin →
  2. Bypass "sign in with twitter" when using browser embedded in native Twitter app

    If you are using a native Twitter app such as the Twitter app on Android, if you click on a link to a website, which uses "sign in with twitter" to authenticate the user, the user is forced to login again, even though they are already authenticated with Twitter in the native app.

    In a perfect world this secondary sign in would not be necessary, and would reduce a lot of friction.

    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  ·  General features  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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 →
  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!

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

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

    We’ll send you updates on this idea

    under review  ·  8 comments  ·  General features  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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 →
  7. Twitter follow/unfollow Limits

    Hi, I'd love for twitter to readjust the current Follow/unfollow Limits currently set for each app.. we understand these limits are being set to eliminate spam activities on twitter but there should be an exclusion to this rule. for example there could be restrictions as to who can be followed or unfollowed (spammed) by the app/service and this should be limited to only those that use the same service/app reason being that the users already know what they're getting into. the funny thing is - users already know how to do these these without even using a 3rd party service.…

    3 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 →
  8. Show app developer profile on app authorization screen

    The app authorization screen that shows up whenever a user is authorizing / logging in using twitter with a twitter app for the first time should also display the app owner twitter account. Like a "Made by: @TwitterAPI ..." box

    As a user, I find it reassuring to see that an app developer has an active presence on Twitter, and as a developer, i'd like to be open about the app purpose and ownership.

    eg: https://developer.twitter.com/content/dam/developer-twitter/images/ScreenShot2015-03-20-authorize-card.png this screen should contain something like the profile popup displaying Name, screen_name, description, whether the account follows me and "Followed by ...…

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

    46 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 →
  10. 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 →
  11. Provide an SLA

    Describe the level commitment (and dedication) to APIs.

    What are the thresholds for usage & overall sunsetting of service?

    What criteria will be used to make significant changes?

    2 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  ·  General features  ·  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…

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

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

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

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

    37 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 →
  17. Tweet translation should be available through the API

    Build a new request operator that can be included in an API request, and returns a translation of the Tweet text in the Tweet payload. Supported languages should be the same languages that are supported by the "lang:" request operator.

    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  ·  General features  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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 →
2 Next →
  • Don't see your idea?

Feedback and Knowledge Base