Twitter Developer Feedback

Iridescence

My feedback

  1. 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  ·  Twitter API » Documentation & Resources  ·  Flag idea as inappropriate…  ·  Admin →
    Iridescence shared this idea  · 
  2. 50 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  ·  Twitter API » General Features  ·  Flag idea as inappropriate…  ·  Admin →
    Iridescence supported this idea  · 
  3. 76 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

    10 comments  ·  Twitter API » Tweet Lookup  ·  Flag idea as inappropriate…  ·  Admin →
    Iridescence supported this idea  · 
  4. 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  ·  Twitter API » Follows  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Iridescence commented  · 

    The documentation at https://developer.twitter.com/en/docs/twitter-api/pagination says all paginated endpoints take `pagination_token` as parameter, but https://api.twitter.com/2/openapi.json says that `GET /2/tweets/(search|counts)/(recent|all)` (4 endpoints) take `next_token` instead.

    The OpenAPI spec also defines the `pagination_token` parameters for `GET /2/users/{id}/(blocking|followers|following)` (3 endpoints) in-place, instead of referencing the `PaginationTokenRequestParameter` component. (There are many other areas in the API spec that use anonymous schemas inconsistently, but that's for another idea.)

    The `TweetSearchResponse` and `TweetCountsResponse` components, which are returned by the endpoints that have `next_token` as parameter, also don't have `previous_token` properties.

    The most consistent and useful solution would be to reference `#/components/parameters/PaginationTokenRequestParameter` for all paginated endpoints, as well as using a consistent response component for the returned `meta` object.

    Iridescence supported this idea  · 
  5. 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  ·  Twitter API » Future of the Twitter API  ·  Flag idea as inappropriate…  ·  Admin →
    Iridescence supported this idea  · 
  6. 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  ·  Twitter API » Future of the Twitter API  ·  Flag idea as inappropriate…  ·  Admin →
    Iridescence supported this idea  · 
  7. 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  ·  Twitter API » Developer Portal  ·  Flag idea as inappropriate…  ·  Admin →
    Iridescence supported this idea  · 
  8. 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  ·  Twitter Developer Labs » General features  ·  Flag idea as inappropriate…  ·  Admin →
    Iridescence supported this idea  · 
  9. 11 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

    acknowledged  ·  0 comments  ·  Twitter Developer Labs » Hide replies  ·  Flag idea as inappropriate…  ·  Admin →
    Iridescence supported this idea  · 
  10. 23 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

    Iridescence supported this idea  · 
  11. 43 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

    acknowledged  ·  5 comments  ·  Twitter Developer Labs » General features  ·  Flag idea as inappropriate…  ·  Admin →
    Iridescence supported this idea  · 
  12. 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

    acknowledged  ·  1 comment  ·  Twitter Developer Labs » GET users  ·  Flag idea as inappropriate…  ·  Admin →
    Iridescence supported this idea  · 
  13. 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

    Iridescence supported this idea  · 
  14. 6 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

    acknowledged  ·  1 comment  ·  Twitter Developer Labs » General features  ·  Flag idea as inappropriate…  ·  Admin →
    Iridescence supported this idea  · 
  15. 98 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

    under review  ·  7 comments  ·  Twitter Developer Labs » General features  ·  Flag idea as inappropriate…  ·  Admin →
    Iridescence supported this idea  · 

Feedback and Knowledge Base