# RSS & Atom Feed Parser (`receptional_blender/rss-atom-feed-parser`) Actor

Turn any RSS or Atom feed into clean, structured JSON — title, link, author, publish date, categories and summary for every entry. Handles RSS 2.0 and Atom, multiple feeds at once. No key, login or proxy required.

- **URL**: https://apify.com/receptional\_blender/rss-atom-feed-parser.md
- **Developed by:** [Assia Fadli](https://apify.com/receptional_blender) (community)
- **Categories:** News
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.01 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## RSS & Atom Feed Parser

Turn any **RSS 2.0** or **Atom** feed into clean, structured JSON. Point it at one or more feed URLs and get back one tidy record per entry — title, link, author, publish date, categories and summary. There is nothing to configure — no API key, no login, and no proxy.

Both dialects are normalised into the **same flat record shape**, so you can mix RSS and Atom feeds in a single run and treat every row the same way.

### Features

- Parses **RSS 2.0** (`<channel><item>`) and **Atom** (`<feed><entry>`) feeds.
- Reads **multiple feeds at once** and merges them into one dataset.
- Normalises both dialects into a single, flat, null-safe record.
- Strips XML namespaces, so `dc:creator`, `atom:link` and friends just work.
- Skips gracefully over a broken feed — it is recorded with an `error` field so one bad URL never stops the run.

### Input

| Field | Type | Default | Description |
| --- | --- | --- | --- |
| `feedUrls` | array | — | One or more RSS 2.0 or Atom feed URLs to parse. |
| `maxItems` | integer | `100` | Maximum number of items to emit across all feeds. |

#### Example input

```json
{
  "feedUrls": [
    "https://hnrss.org/frontpage",
    "https://www.reddit.com/r/programming/.rss"
  ],
  "maxItems": 100
}
```

### Output

Each dataset record looks like this:

```json
{
  "feedTitle": "Hacker News: Front Page",
  "title": "Show HN: A tiny feed parser",
  "link": "https://example.com/article",
  "id": "https://news.ycombinator.com/item?id=8863",
  "published": "2007-04-04T19:16:40.000Z",
  "author": "dhouston",
  "categories": ["show"],
  "summary": "A short description of the entry, as raw HTML.",
  "feedUrl": "https://hnrss.org/frontpage"
}
```

| Field | Description |
| --- | --- |
| `feedTitle` | Title of the channel (RSS) or feed (Atom). |
| `title` | Entry title. |
| `link` | Entry URL (RSS `<link>`, or the Atom `alternate` link). |
| `id` | Entry identifier (RSS `<guid>` or Atom `<id>`). |
| `published` | Publish date as an ISO 8601 timestamp (`null` if unparseable). |
| `author` | Author name (RSS `<author>`/`<dc:creator>` or Atom `<author><name>`). |
| `categories` | Array of category labels. |
| `summary` | Entry summary/description (RSS `<description>` or Atom `<summary>`/`<content>`). |
| `feedUrl` | The feed URL this entry came from. |

If a feed can't be fetched or parsed, the row is `{ "feedUrl": "<url>", "error": "<message>" }` instead.

### Pricing

This actor uses the **pay-per-event** model: you are charged **once per feed item** delivered to the dataset (the `feed-item-scraped` event). A feed that fails to fetch or parse produces an error row and is never charged.

### How it works

The actor fetches each feed over plain HTTP and parses the XML with [`fast-xml-parser`](https://github.com/NaturalIntelligence/fast-xml-parser). It auto-detects RSS vs Atom, coerces single items/entries into arrays, and maps both dialects into one flat record shape. No authentication is required.

### License

MIT © Assia Fadli

# Actor input Schema

## `feedUrls` (type: `array`):

One or more RSS 2.0 or Atom feed URLs to parse.

## `maxItems` (type: `integer`):

Maximum number of items to emit across all feeds.

## Actor input object example

```json
{
  "feedUrls": [
    "https://hnrss.org/frontpage",
    "https://www.reddit.com/r/programming/.rss"
  ],
  "maxItems": 100
}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "maxItems": 100
};

// Run the Actor and wait for it to finish
const run = await client.actor("receptional_blender/rss-atom-feed-parser").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "maxItems": 100 }

# Run the Actor and wait for it to finish
run = client.actor("receptional_blender/rss-atom-feed-parser").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "maxItems": 100
}' |
apify call receptional_blender/rss-atom-feed-parser --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,receptional_blender/rss-atom-feed-parser"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/MuKwNlJmtT6ubxRGZ/builds/V3gJOGgqdjl2KiIaf/openapi.json