Twitter Developer Feedback

Twitter API

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Un-retweet (or un-like) tweets that are more than a few years old always fail

    Un-retweeting and un-liking tweets that are more than a few years old will always fail. This is a sad situation for users who want to delete their past actions from Twitter. Could you please fix this behavior? For technical details, see https://twittercommunity.com/t/is-a-function-to-fetch-a-list-of-likes-mutes-and-blocks-is-completely-removed-in-api-v2/154375/12

    Japanese version:
    数年以上前のツイートに対する「RTの取り消し」と「いいねの取り消し」は必ず失敗します。ツイッターから過去の行動を削除したいユーザーはこのことに困っています。この振る舞いを修正してもらえませんか? 技術的な詳細はこちらをご覧ください。https://twittercommunity.com/t/is-a-function-to-fetch-a-list-of-likes-mutes-and-blocks-is-completely-removed-in-api-v2/154375/12

    26 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General Features  ·  Flag idea as inappropriate…  ·  Admin →
  2. Allow the archive data to be downloaded from mobile devices

    Users with mobile devices sometimes fail to download the archive data.

    There are various reasons for this, such as not being able to press the download button after failing download the file once, or not being able to download a large file due to narrow bandwidth.

    Please fix the problem so that the archive data can be downloaded properly even in these situations.

    142 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  General Features  ·  Flag idea as inappropriate…  ·  Admin →
  3. Allow users to take control of their own data

    Please ease the restrictions on getting their own friends/followers data.

    Twitter's API restrictions are getting stricter every year, and starting with Twitter API v2, I understand the data that users will be able to retrieve via the API will decrease by 80%.
    Previously, with a single API call, users could retrieve 5,000 friends (or followers), but in the future, users will only be able to retrieve 1,000 friends (or followers). https://developer.twitter.com/en/docs/twitter-api/users/follows/migrate

    I understand that this decision has been made from the perspective of sustainability of the service, but please reconsider restricting users from controlling their own data.

    As one solution,…

    117 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Future of the Twitter API  ·  Flag idea as inappropriate…  ·  Admin →
  4. Allow users to search keywords in the DM direct message channels

    Users are unable to search any words in the DM other than an exact name. This is a significant friction problem.

    If we could search keywords for followers that want us to "notify" or of our Twitter Spaces directly, we could search them.

    If we could search keywords we drop in the DM ourselves, we can quickly reconnect with specific connections.

    It's a problem that if we don't spell someone's name exactly, we can't find their DM messages. This is especially a problem in an international community where we don't know how to spell names or remember them perfectly when…

    20 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Future of the Twitter API  ·  Flag idea as inappropriate…  ·  Admin →
  5. Extra options for Twitter space hosts.

    It would be great if Twitter spaces enables hosts to have an extra options such as to throw confetti, balloons, a fire emoji and a love emoji. This is to entertain and engage with the listeners and speakers.Especially during special occasions such as birthdays, anniversaries or space weddings.

    12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  6. Tweets not returning when user is tagged in Image

    We have observed that we get the tagged information of the users if they are tagged in the text portion of the tweet. However when a user is being tagged in the image we do not get any information about that.
    Can we add these features in next release.

    19 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Tweets: Filter Stream  ·  Flag idea as inappropriate…  ·  Admin →
  7. media.fields should return url for gifs or videos

    Currently url is returned on images only.

    57 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Tweet Lookup  ·  Flag idea as inappropriate…  ·  Admin →
  8. Authentication with Oauth 2.0

    Will there be any ability to do 3rd party authentication with Oauth 2.0, or will it remain in Oauth 1.0a?

    54 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  9. Batch/Bulk V2 API request for get follower/ids, follower/lists

    Batch/Bulk V2 API request for get follower/ids, follower/lists

    Use case: Follower social graph- To get insights on followers (topic of interests, user profile location), need to make multiple API calls to the follower end points and its hard with rate limits. Can we have a bulk API request?

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Follows  ·  Flag idea as inappropriate…  ·  Admin →
  10. Allow Users To React To Direct Messages

    Currently the is no ability to react to messages,

    Adding this can help third party applications building optimized conversations for companies and bring the full features of direct messaging

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Future of the Twitter API  ·  Flag idea as inappropriate…  ·  Admin →
  11. Dedicated Bot Accounts

    Enable creation of dedicated "bot" accounts, solely for posting tweets or other automated activity. These would display with a 🤖 robot emoji by the name (instead of a blue checkmark) so they are easily distinguished from regular users.

    Self-selecting into the "bot" category could come with a different, more restrictive set of permissions - no web login or posting (OAuth only), cannot Follow others, or whatever other limits Twitter wants to impose on them. On the flip side, bots could enjoy different categories of moderation, suspension, or flagging rules as they are no longer being confused with "human" posters. No…

    48 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  General Features  ·  Flag idea as inappropriate…  ·  Admin →
  12. List Discovery API v2 Endpoints

    As a developer of a command line client, I would like to provide a way for users to discover new lists based on a specified criteria, similar to the Discover New Lists in the web UI.

    Being able to search against the name and description fields would beneficial, in addition to the same algorithm used in the web UI.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  General Features  ·  Flag idea as inappropriate…  ·  Admin →
  13. Stop spammers using your t.co shortening machine to hide their dangrerous links.

    At the moment there are a serious Bank information collecting attack in e-mails. Many of the dangerous links have been hidden by the t.co shortening. One cannot solve where the links are leading, so there is no possibility to block these dangerous addresses out from the web.
    Net criminals will thank Twitter about this support.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Tweets: Users  ·  Flag idea as inappropriate…  ·  Admin →
  14. Retain rate_limit_status in v2

    One of the important endpoints we use in v1.1 is applicaiton/ratelimitstatus
    It appears that there is no plans to replace this endpoint in v2.

    This endpoint cannot be replaced with headers alone. Headers are only useful for subsequent calls.
    But this endpoint helps understand if we can make calls to certain endpoints, especially in multi-server deployments and service restarts, otherwise we end up with having to make a lot of unnecessary calls and get error responses when the rate limit is at zero

    I request this endpoint is retained in v2

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Future of the Twitter API  ·  Flag idea as inappropriate…  ·  Admin →
  15. Search by minimum retweets and likes in API 2

    Being able to search by minimum number of favourites and retweets as we could in API 1.1 would be great to see in Recent search API 2. This is particularly useful for a large volume of tweets, and being able to find the tweets with the most engagements.

    35 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Tweets: Search  ·  Flag idea as inappropriate…  ·  Admin →
  16. Filter Stream API: Operator rule to "return more than X tweets per second" vs. specifying a percentage sample

    A rule operator of "no more than X tweets per second" is very similar to sampling. However, if it existed, it could theoretically set on every rule. This would allow knowing that no rules could absorb too much of total allowed volume, and to make sure that low volume rules aren't sampled, while higher volume rules still are. It would also mean that a rule that has a sudden burst of activity would not absorb all available volume at once. Without this operator, monitoring the volume on rules must take place, and sampling must be applied dynamically when volume increases…

    21 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Future of the Twitter API  ·  Flag idea as inappropriate…  ·  Admin →
  17. Filtered Stream limits after Early Access

    The current limit for filtered stream is very small compared to the v1.1 API and we have no idea on the paid option to have increased limits on rules, characters per rule and total tweets. Is hard to plan ahead some features with the current information.
    Can you provide the information on paid tiers of that endpoint? It's a big change to leave us without knowing is it even possible to pay for enough limit.

    40 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Tweets: Filter Stream  ·  Flag idea as inappropriate…  ·  Admin →
  18. Change the rate limit for the recent search endpoint

    Please consider changing the current rate limit for the recent search endpoint (v2 API). Currently an app can only fetch a total of 500k tweets in a monthly window, no matter how many active Twitter users it has, or if the requests are per-user. If an app has over 500k active user then there's no way for the app to function correctly due to this limit.

    In my case we're offering people to fetch hashtagged posts from Twitter for free, which is very popular for all kind of events, such as weddings and virtual conferences. We're not able to provide…

    34 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Tweets: Search  ·  Flag idea as inappropriate…  ·  Admin →
  19. Add endpoint for fetching authorized user using access token & secret [/@me]

    Currently the only way to fetch a user is by either using ID or username, which is great for most usecases. However, most of the endpoints need the authorized user's ID in the path. As a library dev I don't want to force the user to pass the authorized user's ID everytime they call a method. So, as a workaround I ask them to pass the "username" along with other credentials during login. Then I use that "username" to fetch the authorized user and save it in the cache. This way I can automatically pass the authorized user's ID internally…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Future of the Twitter API  ·  Flag idea as inappropriate…  ·  Admin →
  20. API with Spaces

    Spaces would be great to be included within the API. That will open the gates of opportunities for developers to integrate them into their apps.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Future of the Twitter API  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 12 13
  • Don't see your idea?

Feedback and Knowledge Base