Twitter Developer Feedback

Twitter API

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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,…

    121 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 →
  2. 32 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  ·  Future of the Twitter API  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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…

    24 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 →
  4. 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 →
  5. API endpoint to get monthly tweet quota data - return both usage and expiration

    It appears that you are now enforcing a monthly cap on the number of tweets we can obtain via API.

    This request is for programmatic access to this quota information. In particular, it would be helpful to retrieve both the number of tweets fetched for the current month, and the reset date. Thanks!

    See here for specifics:

    https://twittercommunity.com/t/filtered-stream-v2-how-to-get-monthly-limits-info/141702

    10 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 →
  6. Media includes missing a number of important fields

    The variants data is missing, making videos impossible to play inline.

    The embeddable field is also missing, this is used to indicate that the photo media is actually a video that can only be played in a web browser.

    extalttext is missing.

    10 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  ·  Future of the Twitter API  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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

    8 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 →
  8. Entity "media" URLs should have a media_key

    This (pastebin.com/WGD0fp8D) is a Tweet that has a couple random links, a manually pasted in link to a Twitter photo and an uploaded photo.

    When parsing entities.urls, there should be a way match the two image entity URLs to a media_key.

    Problem #1. There’s no indication that a particular URL is a media URL.

    Problem #2. There’s no direct key to match the appropriate attachment.

    Adding a media_key KV to the entity.urls would fix these two problems.

    8 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 →
  9. Adding the 'url' option in media.fields for videos

    As in the title. The 'url' object is available for still images, but not for videos. This make absolutely NO SENSE. I would've thought this would be a major feature, and I wonder why it hasn't been included.....

    The exclusion of this will affect thousands of API users, in my opinion.

    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  ·  Future of the Twitter API  ·  Flag idea as inappropriate…  ·  Admin →
  10. Think of end to end tests

    When developing the endpoints please consider how you would write end to end tests.

    In v1.1 end to end tests can be complicated to write. Not only is there the challenge of timeouts and replication of the data on your server but also some of the endpoints just stop working temporarily.

    Over the years I have reported many bugs that could have been prevented if Twitter did have end to end tests.

    Please do think about writing these tests and think through how developers of libraries can write similar tests.

    You can find my end to end tests collection here…

    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

    0 comments  ·  Future of the Twitter API  ·  Flag idea as inappropriate…  ·  Admin →
  11. /2/tweets/:id should support a username query argument

    Fetching individual or lists of users via ID is obviously always preferable, but there's cases when that's simply not possible.

    The v1.1 API had option to pass in username/screen_names instead of IDs and it'd be great if v2 had the same option.

    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

    2 comments  ·  Future of the Twitter API  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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 →
  13. 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 →
  14. Make the API response object better structured

    Currently, a response object like a tweet has a data field and includes field. This structure isn't really helpful, as the author is sent inside this "includes" field which also has other users, like a mentioned user. Instead of adding extra fields inside a totally seperate "includes" object, add these inside the "tweet" object itself. Like put the user who tweeted inside the "tweet.author" and the mentioned users inside "tweet.mentions" or something. These fields will not be present when they are not opted but will be present when opted in. This structure will really help library developers like me. As…

    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. 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 →
  16. WebSockets API for real-time events

    It would be nice to have a WebSockets API for recieving real-time events for tweet create/delete, like/unlike, DMs and for many other events. You can look at Discord's Gateway for example. It will help you save resources as users won't be doing frequent requests to simulate these events and will also help developers create really cool things. I hope you have something like this planned.

    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

    0 comments  ·  Future of the Twitter API  ·  Flag idea as inappropriate…  ·  Admin →
  17. Allow to add polls to tweet via python

    Polls can't be added to "update status tweet".
    It should be allowed to post poll via python coding, simple as that
    One could obtain info from tweets, arrange information to sort for best possible choices, and then post a poll.

    Only step in procedure that can't be done is to post poll.

    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

    0 comments  ·  Future of the Twitter API  ·  Flag idea as inappropriate…  ·  Admin →
  18. Make Poll API which can all polls for a particular user.

    Like many developers have questions like below:

    1) I wanted to know like can I get all polls data for a user?
    2) Is there any API exist that will give me the details of the poll for a certain user?
    3) can we get all polls data for a user since a user has been created? If yes then How?

    So if Twitter can make an API that satisfies the above requirement.

    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

    0 comments  ·  Future of the Twitter API  ·  Flag idea as inappropriate…  ·  Admin →
  19. API, token (key secret key) in code

    I write API, token (key secret key) in code but it didn't give me results or information about data to assess, analysis and clean.

    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

    2 comments  ·  Future of the Twitter API  ·  Flag idea as inappropriate…  ·  Admin →
  20. Mention entities should include ID of user

    Mention entities currently only include the username of the mentioned user. It'd be great if it was possible to add a entities.mentions.id expansion (or if it just came out by default) to get the author id of the mentioned user.

    This is specially useful for the V2 APIs since /2/tweets doesn't have a username query argument and in some cases /2/tweets/ you'll get a mention without the matching user includes.

    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

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

Feedback and Knowledge Base