Following Feeds

Following relationships are a fundamental part of social networks and many other apps that feature feeds. They link one Feed to another and cause Activities added to a feed to appear in any other feeds that follow it.

When an Activity is added to a feed, it is automatically added to any other feeds that follow the feed. This does not propagate further through the graph of following relationships. If your app requires that the Activity be added to other feeds, "to" field targeting or a batch activity add may be suitable.

The code example below shows you how to follow a feed:

Also take note that:

By default, the most recent 100 existing activities in the target feed will be added to the follower feed, but this can be changed via the activity_copy_limit parameter.

If you need to follow many feeds at once have a look at how to batch follow later in this document. If you need to run large imports, use our JSON import format.

Unfollowing a feed removes the following relationship with the feed specified in the target parameter. See the following examples:

Existing Activities in the feed that originated in a no longer followed target feed will be purged unless the keep_history parameter is provided.

Returns a paginated list of the given feed's followers. See the following example:

The followers returned by the API are sorted reverse chronologically, according to the time the follow relationship was created.

Returns a paginated list of the feeds which are followed by the feed. See the following example:

The followed feeds returned by the API are sorted reverse chronologically, according to the time the follow relationship was created.

Paginating followers and/or followings is sometimes not the answer and only counts are needed. In this case, stats can be retrieved directly too. With default permissions, it works automatically for server side auth. For client-side auth, please contact support to add it to your required feed groups.