RSS feed

GET /v1/articles.rss

Returns the same results as GET /v1/articles formatted as RSS 2.0. All query parameters and plan rules apply identically.

curl -G 'https://api.presscloud.ai/v1/articles.rss' \
  -H "Authorization: Bearer $PRESSCLOUD_API_KEY" \
  -d country=NL \
  -d q=overname

The response has Content-Type: application/rss+xml; charset=UTF-8.

<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:pc="https://presscloud.ai/ns/news">
  <channel>
    <title>Presscloud News API, country=NL, q=overname</title>
    <link>https://api.presscloud.ai/v1/articles.rss</link>
    <language>nl</language>
    <lastBuildDate>Thu, 20 Aug 2026 07:44:00 GMT</lastBuildDate>
    <item>
      <title>Amsterdamse scale-up haalt 12 miljoen op voor uitbreiding naar Duitsland</title>
      <link>https://www.example.nl/artikel/...</link>
      <guid isPermaLink="false">art_5c31b0</guid>
      <pubDate>Thu, 20 Aug 2026 07:42:00 GMT</pubDate>
      <author>Joris de Vries</author>
      <pc:outlet domain="example.nl">Example Zakelijk</pc:outlet>
      <pc:country>NL</pc:country>
    </item>
  </channel>
</rss>

Channel

The channel title lists the applied filters, so feeds with different parameters are distinguishable in a reader. Parameters at their default value — search=keyword, search_in=title, order=desc — are omitted from the title.

The channel language is set when it can be determined unambiguously: a single language filter, or a single country. Otherwise it is omitted.

Extension elements

Fields without a standard RSS 2.0 element use the pc namespace (https://presscloud.ai/ns/news). Readers that do not recognise the namespace ignore these elements.

Element	Description
pc:outlet	Outlet name, with the domain as a domain attribute.
pc:country	NL, BE or LU.
pc:relevance	Relevance score. Semantic search only.

Field mapping

RSS	JSON
guid	id
title	title
link	url
pubDate	published_at (RFC 822)
author	authors[].name
pc:outlet	outlet.name, outlet.domain
pc:country	country
pc:relevance	relevance

snippet is not included in the feed.

Limitations

The feed requires the same Authorization header as the JSON endpoint. Readers that cannot send custom headers should consume the feed through an intermediary service.

The feed returns a single page of up to 100 items (per_page). For complete result sets, use the JSON endpoint with pagination.