Would be useful to determine if a user is using an NFT avatar or not via the User object, in the same way we can determine if a user is verified.1 vote
User lookup returns fields like "protected", "withheld" and "verified" but there are no fields for suspended, restricted and deleted accounts.23 votes
Would be nice to have an endpoint to know who blocked a specific user.
We already have an endpoint to have the blocking users but the opposite doesn't exist.1 vote
There should be an endpoint to get the user data corresponding to the tokens provided instead of manually providing the user id as the tokens are provided per user per app.2 votes
The v2 API "/2/users" missing the user profile banner image (a.k.a "profilebannerurl" in v1). Please add it back so we not have to request the API twice.12 votes
Many fields that were previously available in /1.1/users/lookup.json are not available in v2 2/users/:id
Are those fields officially deprecated or would it be possible to add them ?
v1.1 supports a GET user/search which is limiting in many ways:
- limited to 1000 users
- results are not relevant to the authenticated user
- does not respect the blocked user rule (blocked users show up in the search results)
The v2 API returns the User object without a relationship between the authorized query user with other users. And v1 API returns isFollow/followingPending attributes in the User object.
I believe one of the v2 API design targets is to reduce the API query count. So adding a friendship expansion in the query will help.
Hi There, I am looking to get a user birthday from the user lookup to build a greeting mechanism for user & followers.
It’ll be good to have this information for the user with authentication if it cannot be made publicly available. Thanks1 vote
It seems that the new v2 user lookup endpoint doesn’t return the latest tweet posted by the user(s). It was previously provided by the v1.1 API and was quite powerful (for example) to determine the latest datetime a user was actively (re)tweeting, without having to call the user_timeline endpoint (that is currently inconveniently limited to 100k calls a day (per app)).
Would it be possible to add it back on v2 under a “latest_tweet_id” field?
I am aware that the pinned tweet id is returned, but it doesn’t satisfy my needs.4 votes
Create a dedicated section to save the daily stories and make them on the face of the personal account in a smooth and clear manner, like what is present on Instagram, so we have completed a new and important section2 votes
Right now, it does not seem possible to run emoji-based queries for users through the API, while it is possible in web searches. Would be awesome to enable this feature for API queries in v2! See thread here: https://twittercommunity.com/t/cannot-query-by-emoji-using-search-user-through-tweepy/147103/41 vote
Showing 0 Followers and 0 Following on user Profile even though user have followers and following on users upon reactivating account :)1 vote
What do Your Backup log
not bad?1 vote
- Don't see your idea?