Batch/Bulk V2 API request for get follower/ids, follower/lists
Use case: Follower social graph- To get insights on followers (topic of interests, user profile location), need to make multiple API calls to the follower end points and its hard with rate limits. Can we have a bulk API request?2 votes
Follows are social media currency. Often, when one follows an account, the account followed then mutes the follower. It is important that followers have this information. Maybe even structure a call to see which accounts have muted you...much like the which lists you appear on api call.1 vote
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_atdate 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
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 please2 votes
We look forward to hearing what you think of the new follows lookup endpoints.1 vote
Why have the inconsistency between parameter
next_tokenand others use
in the response
next_token; so it should be better if all can be unified as parameter
- Don't see your idea?