LoopFeed API Reference

The LoopFeed API provides programmatic access to content aggregation and publishing features. This documentation covers all available endpoints for gettings all the projects for your organization, getting topics for a project, retrieving published content, and monitoring content counts.

Quick Start

1. Get All Projects

   Get a list of available projects for your organization.

2. Get All Topics for a Project

   Get a list of available topics for a project.

3. Get Content Count for a Topic

   Get the number of published content items for a topic.

4. Get Published Content for a Topic

   Retrieve the actual content items with filtering and pagination options for a topic.

Base URL

All API requests are made to:

Base URL

https://q.loop-feed.com/v1/

Authentication

/v1/projects/.. API requests require authentication. Use X-Api-Key header to pass your API key.

X-Api-Key: <api-key>

You can create the API key from LoopFeed dashboard. Navigate to “Settings” -> “API Keys” and click on “Create API Key”.

Generate the key with the default scopes and copy the key:

Use this key in the X-Api-Key header for all the protected endpoints.

Copy API Key

You can copy the API key by clicking on the “Copy” button. It won’t be shown again after you leave the page. If you lose the key, you can create a new one, but you won’t be able to access any existing key.

API Endpoints

Get All Projects

Authentication Required

X-Api-Key header is required for this endpoint.

Get a list of available projects for your organization.

GET /v1/projects

Get All Topics for a Project

Authentication Required

X-Api-Key header is required for this endpoint.

Get a list of available topics for a project.

    GET /v1/project/<project-id>/topics

Get Content Count for a Topic

Get the number of published content items for a topic.

    GET /v1/topic/<topic-id>/count

Get Published Content for a Topic

Retrieve the actual content items with filtering and pagination options for a topic.

    GET /v1/topic/<topic-id>/content

---

1. Get All Projects

Authentication Required

X-Api-Key header is required for this endpoint. Authentication

Get a list of all the projects for your organization. Projects are the top-level entities in LoopFeed and are used to group topics, widgets, queues etc.

Request

GET https://q.loop-feed.com/v1/projects

Headers

Header	Type	Description
X-Api-Key	String	Required: Your API key

Response

Success Response

[
  {
    "id":"id-of-the-project",
    "name":"name-of-the-project"
  },
]

Schema

Property	Type	Description
id	String	ID of the project
name	String	Display name of the project

---

2. Get Topics for a Project

Authentication Required

X-Api-Key header is required for this endpoint. Authentication

Get a list of all the active topics for a specific project. Refer to the topic creation guide for more information on how to create and configure a topic.

Request

GET https://q.loop-feed.com/v1/project/<project-id>/topics

Headers

Header	Type	Description
X-Api-Key	String	Required: Your API key

Parameters

Parameter	Type	Description
project-id	String	Required: ID of the project

Response

Success Response

  [
    {
      "id":"id-of-the-topic",
      "name":"name-of-the-topic",
      "url":"https://q.loop-feed.com/v1/content/id-of-the-topic",
      "metadata":null
    }
  ]

Schema

Property	Type	Description
id	String	ID of the topic
name	String	Display name of the topic
url	String	URL to fetch content for this topic
metadata	Object	Metadata for the topic.

3. Get Content Count for a Topic

Get the number of published content items for a topic.

Request

GET https://q.loop-feed.com/v1/topic/<topic-id>/count

Parameters

Parameter	Type	Description
topic-id	String	Required: ID of the topic

Query Parameters

Parameter	Type	Description
service	String	Optional: Filter by service (twitter, youtube, instagram, rss)
since	Integer	Optional: Unix timestamp - content published after this time
until	Integer	Optional: Unix timestamp - content published until this time
limit	Integer	Optional: Number of results (default: 20)
offset	Integer	Optional: Pagination offset (default: 0)

Response

Success Response

{
  "count": 256
}

Schema

Property	Type	Description
count	Integer	Number of published content items for the topic

Efficient Content Monitoring

Use the count endpoint with the since parameter to check for new content before making expensive content fetch requests.

---

4. Get Published Content

Retrieve published content items for a specific topic. This is the main endpoint for getting actual content data.

Request

GET https://q.loop-feed.com/v1/topic/<topic-id>/content

Parameters

Parameter	Type	Description
topic-id	String	Required: ID of the topic

Query Parameters

Parameter	Type	Description
service	String	Optional: Filter by service (twitter, youtube, instagram, rss)
since	Integer	Optional: Unix timestamp - content published after this time
until	Integer	Optional: Unix timestamp - content published until this time
limit	Integer	Optional: Number of results (default: 20)
offset	Integer	Optional: Pagination offset (default: 0)

Response

Success Response

[
  {
    "id": "6fc9c511ab95bbd83f8478437a2f87ff1fc4f365",
    "service": "rss",
    "type": "link",
    "title": "Premier League fixture rescheduled",
    "text": "Our forthcoming Premier League fixture against Burnley has been rescheduled",
    "url": "https://www.arsenal.com/news/premier-league-fixture-rescheduled-0",
    "date": "2022-01-09T17:10:00.000Z",
    "author": {
      "name": "arsenal",
      "username": "arsenal"
    },
    "media": [
      {
        "type": "image",
        "url": "https://www.arsenal.com/sites/default/files/styles/desktop_16x9/public/images/DSC_2115_2021050642150098.JPG?itok=-0Af-IiL"
      }
    ],
    "kudos": {
      "score": 0,
      "rss_score": 0
    },
    "language": "en"
  }
]

Content Item Schema

Property	Type	Description
id	String	Unique identifier for the content item
service	String	Source platform (twitter, youtube, instagram, rss)
type	String	Content type (video, image, link, status, embed, comment)
title	String	Content title (may not be available for all content types)
text	String	Content text/description (may contain HTML)
tags	Array	Array of content tags
url	String	URL to original content on source platform
date	DateTime	Publication date in ISO 8601 format
author	Object	Author information with name and username
media	Array	Attached media (images, videos, embeds)
kudos	Object	Engagement metrics (likes, shares, etc.)
language	String	Content language (ISO 639-1 code)

---

Complete Workflow Example

Here’s a complete example showing the recommended workflow for efficiently working with the LoopFeed API:

// 1. Get all projects for your organization
const projectsResponse = await fetch('https://q.loop-feed.com/v1/projects', { headers: { 'X-Api-Key': 'your-api-key' } });
const projects = await projectsResponse.json();

// Choose a project from the list
const projectId = projects[0].id; // Choose your project from the previous step

// 2. Get all active topics for the project
const topicsResponse = await fetch(`https://q.loop-feed.com/v1/project/${projectId}/topics`, { headers: { 'X-Api-Key': 'your-api-key' } });
const topics = await topicsResponse.json();

// Ideally, we should store all the projects and topics in a database here for later use.
// You can have a cron job to fetch the projects and topics from the API.

// Choose a topic from the list
const topicId = topics[0].id; // Choose your topic from the previous step

// 3. Get content count for the topic
const countResponse = await fetch(`https://q.loop-feed.com/v1/topic/${topicId}/count`);
const countResult = await countResponse.json();

console.log('Content count for the topic:');
console.log(countResult.count);

// 4. Fetch new content for the topic
const contentResponse = await fetch(`https://q.loop-feed.com/v1/topic/${topicId}/content`);
const content = await contentResponse.json();

console.log('New content:');
content.forEach(item => {
  console.log(`- ${item.service} ${item.type}: ${item.title}`);
});

// 5. Update your last fetch timestamp (recommended)
// You can store the last fetch timestamp in a database and use it to fetch only new content in subsequent requests.
// saveLastFetchTimestamp(Math.floor(Date.now() / 1000));

// Subsequennt requests should use the last fetch timestamp to fetch only new content.
// const contentResponse = await fetch(`https://q.loop-feed.com/v1/topic/${topicId}/content?since=${lastFetchTimestamp}`);
// const content = await contentResponse.json();

// console.log('New content:');
// content.forEach(item => {
//   console.log(`- ${item.service} ${item.type}: ${item.title}`);
// });

Pagination Example

For large result sets, use pagination:

async function fetchAllContent(topicId, since = null) {
  let allContent = [];
  let offset = 0;
  const limit = 100; // Maximum per request

  while (true) {
    const response = await fetch(`https://q.loop-feed.com/v1/topic/${topicId}/content?limit=${limit}&offset=${offset}&since=${since}`);
    const content = await response.json();

    if (content.length === 0) break; // No more content

    allContent.push(...content);
    offset += limit;

    // Break if we got less than the limit (last page)
    if (content.length < limit) break;
  }

  return allContent;
}

---

Branding Guidelines

Legal Requirement

When displaying content from social media platforms, you must follow their respective branding guidelines. Failure to comply may result in access revocation or legal action.

Twitter

Brand Toolkit

Twitter Brand Guidelines →

• Use official Twitter logo and colors
• Include proper attribution
• Link back to original tweets

YouTube

Developer Guidelines

YouTube Branding Guidelines →

• Use official YouTube logo and play button
• Include video attribution
• Display accurate metadata

Instagram

Brand Resources

Instagram Brand Guidelines →

• Use official Instagram logo
• Include user attribution
• Respect privacy settings

Implementation Requirements

When displaying content, ensure:

• ✅ Official logos are used correctly
• ✅ Proper attribution is included
• ✅ Links back to original content work
• ✅ Brand colors match official guidelines
• ✅ Required disclaimers are present
• ✅ Terms of service are followed

---

Rate Limits & Best Practices

Efficient API Usage

• Use the count endpoint before fetching content to avoid unnecessary requests
• Implement pagination for large result sets
• Store timestamps to fetch only new content
• Cache responses when appropriate
• Respect rate limits and implement exponential backoff

Performance Tips

1. Check counts first: Always use the count endpoint to determine if new content is available
2. Use timestamps: Leverage since parameters to fetch only new content
3. Implement caching: Cache responses locally to reduce API calls
4. Batch requests: Use maximum count values (100) to minimize request numbers
5. Handle errors gracefully: Implement retry logic with exponential backoff