Feeds API Overview
The Feeds API allows your application to display personalized content feeds, similar to what a user would see in the Firstup web or mobile experience.
Each feed is tailored to the authenticated user, meaning users only see content they’re permitted to access based on their role, group membership, and platform rules.
UI Example

How Feeds Work
At the core of the Feeds API is a filtering system that helps you deliver targeted content to your users.
You can customize feeds using a variety of filters, such as:
channels.id
– Filter posts by specific topics or channels.content_type
– Limit results to articles, videos, links, images, notes, etc.visibility
– Show only public, private, or any visibility level of content.
The API also supports named feeds. This set of filters can be accessed using the name
query parameter. Examples include:
myfeed
– Posts the user has access to (not limited to what they follow)following
– Posts from followed topics or channelstrending
,bookmarked
,featured
,community_images
, and more.
You’ll find the full list of supported feed names in the API documentation for listFeedPosts
.
Dynamic Content
Feeds are dynamic, meaning the content updates frequently based on new posts, user interactions, and platform algorithms. As a result, there’s no total count of records. However, the API supports standard pagination parameters (page.size
and page.number
) to help you control how many results are returned at a time.
Look at our Pagination documentation for more information.
Interactive Content
Just like in the member experience, users can interact with posts directly through the API. Supported actions include:
- Liking a post
- Bookmarking content
- Responding to polls
These interactions can be integrated seamlessly into your app’s UI to create a consistent and engaging user experience.
Feeds Endpoints
Feeds endpoints work by an authenticated user. See our Authorization and Authentication article for more help.