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

    31 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 →
  2. 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 →
  3. 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…

    28 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 →
  4. 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.

    25 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 →
  5. 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.

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

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

    31 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 →
  8. 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 →
  9. Help developers filter out spam or other noisy content

    There can be a huge upfront effort to sift through the volume of Tweet data in order to get a data set that is interesting and valuable. It would be great to add more upfront filtering options to reduce the amount of data needed for statistically relevant analysis.

    5 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  ·  Tweet Annotations  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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 →
  11. Provide developers with an app usage tracking tool

    Twitter could include a tool in the developer portal that enables developers to monitor and manage usage across the different APIs, and helps them avoid unexpected rate limiting.

    5 votes
    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 →
  12. Recommend and endorse a good Twitter library

    Twitter could include a list of approved Twitter libraries for different programming languages in the documentation. This would equip developers with robust resources and help them know which resources they can rely on to use the Twitter API.

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

    We’ll send you updates on this idea

    started  ·  7 comments  ·  Documentation and resources  ·  Flag idea as inappropriate…  ·  Admin →
  13. Provide developers with an API testing console

    As a new developer, I want a lightweight way to make an API call within the documentation with little setup involved. I need to see and evaluate quickly what a request and response looks like for a specific endpoint.

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

Feedback and Knowledge Base