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. 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 →
  2. 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 →
  3. 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 →
  4. 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  ·  0 comments  ·  General features  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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.

    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  ·  GET users  ·  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. 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 →
  8. Longer queries in filtered stream

    Queries can only contain a limited number of terms and characters. It would be very useful to increase this llimit.

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

    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  ·  Recent search  ·  Flag idea as inappropriate…  ·  Admin →
  10. Allow to access historical replies for a depth of a year for subscribed users

    As hiding criterias tend to change over time (eg global grey-list of unwanted commenters to hide), I wish my app would be able to retroactively access (and hide/unhide) historical replies to historical tweets of subscribed users with a depth of eg at least a year from now.

    At least, to access the list of replies my app had previously hidden.

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

    Thanks for the feedback! This is not currently on our roadmap, but keeping track of the replies that have been hidden by your app should be fairly straightforward to do on your end. It would be helpful if you could give us additional insight into why this feature is important for you and tell us more about your use case.

  11. Allow to serve 10Ks-100Ks of users subscribed for a HideReplies app

    Allow a free-plan developer to serve 10Ks-100Ks of users subscribed for a "hide replies" allowing to hide tweets nearly real-time as they happen (provided that an app is capable to deal with such a firehose).

    This at least requires easy access to a stream of direct and indirect replies to the users subscribed.

    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  ·  Hide replies  ·  Flag idea as inappropriate…  ·  Admin →
  12. Programmatically unhide a Tweet

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

    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  ·  Hide replies  ·  Flag idea as inappropriate…  ·  Admin →
  13. Richer Direct Messaging API to enable creating more powerful BOTs

    To enable a truly rich bot experience on Twitter, the API is missing things like:
    - Cards message type (image + text + buttons +swipe left/right)
    - Buttons and menus as part of message (not only Quick Replies)
    - A more integrated webview, that is an integral part of the bot experience (for example the bot sends a "pick your seat" button which opens a small size web widget right in the chat to pick the seat, and then goes back to the main chat bot flow)
    And most important:
    the fixed limit of 15k DM regardless of number of…

    2 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 →
  14. 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 →
  15. 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 →
  16. 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 →
  17. 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 →
  18. 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 →
  19. 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 →
  20. Twitter and users improvements

    Adding a trial or a demo developer account would be a great and fantastic idea because it well help the users to try something new and make them very interesting and in the other hand it well help twitter seeing their actions and knowing if they are able to be responsible of the developer account or not.

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

Feedback and Knowledge Base