RSS Feed to JSON Converter: RSS & Atom Feeds
Pricing
from $0.20 / 1,000 feed entry extracteds
RSS Feed to JSON Converter: RSS & Atom Feeds
Read public RSS 2.0, RSS 1.0 (RDF), and Atom feeds and add one clean JSON dataset item per feed entry. The Actor keeps publication metadata and a public author name, strips HTML from summaries, follows robots.txt, and refuses private network destinations.
Pricing
from $0.20 / 1,000 feed entry extracteds
Rating
0.0
(0)
Developer
PlainKit bin
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Features
Share
RSS Feed to JSON
Introduction
RSS Feed to JSON provides robust extraction, acting as an RSS 2.0, RDF and Atom parser that converts public syndication feed entries to structured JSON items. It fetches public feeds with strict robots-aware compliance, parses channel elements, normalizes publication dates to UTC ISO 8601 strings, cleans HTML tags from summaries, and preserves public author names, categories, and GUID identifiers.
Use cases
- News and blog monitoring: Ingest latest entries from multiple public RSS 2.0, Atom, and RDF feeds for content aggregation or sentiment tracking.
- Data ingestion pipelines: Collect post titles, canonical links, publication timestamps, and summaries directly into analytics warehouses.
- Workflow automation: Trigger downstream alerts or notifications based on newly published feed items.
Tutorial
Step-by-step guide
- Prepare a JSON input object containing
feed_urlswith 1 to 20 public RSS 2.0, RSS 1.0/RDF, or Atom feed links, and optionally configuremax_itemsandmax_feeds. - Run the Actor on the Apify platform or start a run via the Apify API.
- The Actor verifies
robots.txtcompliance, downloads each feed, parses entries, strips markup from summaries, and scrubs sensitive contact details. - Retrieve the extracted dataset items in JSON, CSV, or Excel format.
Pricing
The Actor is billed per extracted feed entry under the Pay-Per-Event model using the feed-entry-extracted event.
| Usage tier | USD per feed entry | Largest input bill (10,000 items) |
|---|---|---|
| FREE | $0.0003 | $3.00 |
| BRONZE | $0.00027 | $2.70 |
| SILVER | $0.00024 | $2.40 |
| GOLD | $0.0002 | $2.00 |
| PLATINUM | $0.0002 | $2.00 |
| DIAMOND | $0.0002 | $2.00 |
The largest allowed input (20 feeds at 500 entries per feed) yields at most 10,000 entries, resulting in a maximum bill of $3.00 on the FREE tier ($2.70 on BRONZE, $2.40 on SILVER, and $2.00 on GOLD, PLATINUM, and DIAMOND). A default run of 5 feeds at 100 entries costs up to $0.15. We advise setting a maximum charge per run in the Apify Actor run configuration to ensure costs remain bounded.
Charge contract
Each row is pushed first and charged right after a successful push; a refused charge stops work and that row stays delivered and uncharged; a reached limit stops work after that row was charged; failed items are neither pushed nor charged. Feeds blocked by robots.txt, network errors, or invalid XML produce no dataset entry and are not charged. Any feed URL cut by max_feeds is recorded in STATUS with status skipped and fixed reason code max_feeds. Entries whose guid and link are both empty are skipped (neither pushed nor charged) on both initial runs and restarts, and are counted in the feed status under blank_entries. Rows already in the dataset of a restarted run are skipped and not charged again; if the dataset of a restarted run cannot be read, the run fails with DATASET_READ_FAILED before any new row or charge.
Operational limits
- Accepts 1 to 20 feed URLs per run (
feed_urls). max_feedsdefaults to 5 (configurable from 1 to 20);max_itemsdefaults to 100 (configurable from 1 to 500 entries per feed).- Maximum URL length is 2,048 characters.
- Feed response size is capped at 1,000,000 bytes;
robots.txtresponse is capped at 500 KiB. - HTTP requests have a 20-second timeout, with at most 5 redirects followed.
- Operates within a 300-second execution time budget; if remaining time is below 20 seconds, further fetches stop safely.
Input and output examples
Input example
{"feed_urls": ["https://blog.python.org/feeds/posts/default"],"max_items": 100,"max_feeds": 5}
Output example
{"entry_title": "Python 3.13 Released","link": "https://blog.python.org/2026/10/python-313-released.html","published": "2026-10-07T12:00:00Z","feed_title": "Python Insider","summary": "Python 3.13 is now available featuring performance improvements and new typing features.","author_name": "Python Release Team","categories": ["Releases","Python"],"updated": "2026-10-07T12:00:00Z","guid": "https://blog.python.org/2026/10/python-313-released.html"}
Output fields
| Field | Type | Description |
|---|---|---|
entry_title | String | Title of the specific feed item or story (phone-like digit sequences are replaced by [REDACTED]) |
link | String | URL link returned as the feed gives it and is not resolved |
published | String | Normalized ISO 8601 UTC timestamp of publication |
feed_title | String | Declared title of the parent feed channel (phone-like digit sequences are replaced by [REDACTED]) |
summary | String | Text summary with HTML markup stripped (phone-like digit sequences are replaced by [REDACTED]) |
author_name | String | Public author name when present in feed metadata |
categories | Array | List of category tags associated with the entry (phone-like digit sequences are replaced by [REDACTED]) |
updated | String | Normalized ISO 8601 UTC timestamp of last update |
guid | String | Unique identifier string provided by the feed |
Actor recommendations
Pair this Actor with:
- Readable Article Extractor: Follow links extracted from feed entries to extract complete article bodies and metadata.
- Web Page to Markdown Converter: Convert full blog pages referenced in feed items into clean Markdown documentation.
- CSV and JSON Integrity Parser: Validate and verify structured feed datasets with SHA-256 integrity hashes.
FAQ and support
Which feed formats are supported?
RSS 2.0, RSS 1.0/RDF, and Atom feed formats are fully supported.
Does the Actor fetch full article contents?
No. It parses feed metadata and entry summaries as provided by the syndication feed itself.
Does it track new posts between separate runs?
No. Each execution processes the feed content currently returned by the remote server.
Are phone numbers and digit sequences redacted?
Yes. Phone-like digit sequences in titles, summaries, and categories are replaced by [REDACTED].
Are relative links resolved against the feed URL?
No. The link field is returned as the feed gives it and is not resolved to an absolute URL.
What happens if an entry has neither guid nor link?
An entry whose guid and link are both empty is not pushed and not charged on initial runs or restarts, and is counted in the feed status.
Support and inquiries
For questions, bug reports, or feedback, submit an issue via the Apify Console.