Twitter Developer Feedback

Twitter API

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Timestamps or Snowflake IDs for Follows and Follower links

    Currently there is no way to know when a follow link was established.

    Follows are returned in roughly chronological order, but they should also contain a timestamp created_at date or snowflake id for the relationship.

    This will enable a number of use cases, for example:


    • Measuring Group dynamics and cohesion

    • Community Growth and reach

    • Measuring customer retention

    • Rewarding long term fans / customers

    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  ·  Follows  ·  Flag idea as inappropriate…  ·  Admin →
  2. List of people who follow you that you might have missed

    List of people who follow you that you might have missed
    this way you don't have to go through your followers list to see if you missed anyone & it should be at the top of the "Who to follow" suggestions

    Oh & an EDIT option man please

    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  ·  Follows  ·  Flag idea as inappropriate…  ·  Admin →
  3. Please share your feedback on the follows lookup endpoints

    We look forward to hearing what you think of the new follows lookup endpoints.

    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  ·  Follows  ·  Flag idea as inappropriate…  ·  Admin →
  4. Why have the inconsistency between parameter `next_token` and others use `pagination_token`

    Why have the inconsistency between parameter next_token and others use pagination_token

    https://developer.twitter.com/en/docs/twitter-api/tweets/search/api-reference/get-tweets-search-recent uses next_token
    https://developer.twitter.com/en/docs/twitter-api/users/follows/api-reference/get-users-id-followers uses pagination_token

    in the response meta always uses next_token ; so it should be better if all can be unified as parameter next_token

    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

    0 comments  ·  Follows  ·  Flag idea as inappropriate…  ·  Admin →
  5. blind98211874

    blind2019

    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

    0 comments  ·  Follows  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base