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

    Add more trending stations/places, like for north Indians its only Delhi.

    2 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 →
  3. Add an option to forward a tweet

    To enable one to send a tweet to a group

    1 vote
    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. 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 →
  5. 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 →
  6. 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 →
  7. 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 →
  8. 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 →
  9. 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 →
  10. Data Fixtures for Twitter API's

    Building applications on top of API's are always harder to test. The API's evolve, causing unencountered responses and downtimes.
    App developers are usually late in identifying failure cases when things breakdown. It is why we write tests.

    But with hundreds of API's collecting data for tests is duplication of efforts if someone already have done that.

    To make life easier for all developers, how about a collaborative space where we can dump our data fixtures (Github?)

    I would be glad to contribute as we have been working with Twitter API for the past eight years and have written thousands of…

    2 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  ·  Documentation and resources  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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 →
  12. 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 →
  13. 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 →
  14. 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 →
  15. 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 →
  16. labs/1/users errors collection

    The new error collection is awesome! I am glad that we can now understand why fewer items are returned than requested.
    However, the errors are not always useful, in some cases you get
    status:403
    title:"Forbidden"
    type:"about:blank"
    detail:"Forbidden"


    1. It is not clear which element caused this error since the error index is not correlated with the input id index, ideally there should be a reference to which id caused this error, and the order of the results returned seems random.


    2. It is not clear what's the reason for this error, in cases when we are returning a list, it's probably not…

    2 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 users  ·  Flag idea as inappropriate…  ·  Admin →
  17. GET /labs/1/users compact format feedback

    I like the concept of having compact format in labs/1/users (to reduce the payload), but I don't find it to be very useful in the current format.
    Practically you would want to display a list of users with descriptions and stats, there might be cases when you don't show the description, or don't show stats, but I can't think of a scenario in which you would not show either (i.e. photos and names only)

    1 vote
    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 →
  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. 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.

    10 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 →
  20. Card Validator: Display all meta-tags?

    Description of issue: Could the Card Validator be updated to show all the meta-tags? As it is, it shows the count of metatags, and a somewhat interesting one, like this:


    INFO: Page fetched successfully
    INFO: 23 metatags were found
    INFO: twitter:card = summary_large_image tag found
    INFO: Card loaded successfully

    My request: It would be helpful to display all the tags, not just twitter:card.

    Extra credit: Highlight the tags that Twitter will actually use in the card. This would be helpful when similar tags are present, e.g., twitter:text:title and twitter:title

    URL affected (must be public): https://lochlymelodge.com

    [Troubleshooting steps](https://twittercommunity.com/t/not-whitelisted-unable-to-render-or-no-image-what-to-do-next/62736)

    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  ·  Documentation and resources  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base