The news API that really covers the Benelux
Most news APIs track a few hundred Dutch and Belgian outlets. We track 3,300+ of them. Every article comes back as structured metadata, as clean JSON or RSS, usually within minutes and at most twelve hours after publication.
100 free requests. No credit card needed.
- 3,300+ sources
- 11,200+ articles a day
- 8% with an author name
- Netherlands, Belgium, Luxembourg
- Vermogen prins Bernhard met miljoenen gegroeid in scheidingsjaar RTL.nl 9m ago
- Hoe deze Netanyahu-kenner een van de spannendste verkiezingen ooit in Israël volgt De Stentor 13m ago
- Buurt in Dalfsen vreest dat grote feesten terugkeren in voormalig restaurant: ‘Optelsom baart zorgen’ De Stentor 13m ago
- LUISTER | Op bezoek bij Hennie van der Most: ‘Ik ben alweer bezig, maar ik heb geen geld, niks’ De Stentor 13m ago
Recent articles that entered the index.
Indexed, among others
Global news APIs stop at the top 300
If you have ever queried a global news API for Dutch or Belgian coverage, you know the gap. The national titles are in there. Regional papers, trade media, niche sites, local broadcasters and sector publications are not. In a market where most news lives outside the top 300, that is most of the news.
And the author field is usually empty.
| What you compare | Presscloud News API | Typical global news API |
|---|---|---|
| Dutch sources | 2,600+ | ~300 |
| Belgian sources (NL and FR) | 600+ | ~100 |
| Author name per article | 8% | Rarely |
| Regional and trade media | Yes | Limited |
| Freshness | Minutes to hours | Hours |
Structured, not scraped
Every article comes back as a consistent JSON object. We do not return the full article text. We return everything you need to find an article, classify it and link to it.
- title string
- The headline as the outlet published it.
- url string
- Canonical URL of the article.
- snippet string nullable
- The first 200 characters of the article.
- published_at datetime nullable
- ISO 8601, source time zone normalised to UTC.
- ingested_at datetime nullable
- ISO 8601, when the article entered our index. Poll on this one, not on published_at.
- authors array
- A list of { id, name } objects, with the name as the outlet publishes it. Empty when the outlet credits no author. Filled on 8% of articles.
- outlet object
- Name and domain of the outlet that published the article.
- language enum
- nl, fr, de, lb or en.
- country enum
- NL, BE or LU.
- relevance float search=semantic
- How close this article is to your query, from 0 to 1. It also decides the order of the results.
nullable This field can be null: not every outlet supplies it.
search=semantic You only get this field back on search=semantic. Ask for anything else and it is not in the response at all.
The articles endpoint
Switch filters on and see exactly the request you send. All on one API key.
search- How
qis matched.keywordis the default: a literal match, newest first.booleangives you operators: every word is required, "a quoted run" is matched as a phrase, and a leading minus sign excludes.semanticsearches by meaning, so you also find articles that never use your words. Those come back sorted by relevance, with arelevancescore on every article. sort- Which clock you follow.
published_atis when the outlet published, and it is the default.ingested_atis when the article reached our index: walk that one if you poll for new articles. A slow source can publish today and arrive here tomorrow, by which time a window onpublished_athas already moved past it.
See it before you integrate
Every response has the same structure, as JSON or as an RSS feed. No surprises in production.
{
"status": "ok",
"total_results": 1482,
"articles": [
{
"title": "Amsterdamse scale-up haalt 12 miljoen op voor uitbreiding naar Duitsland",
"url": "https://www.example.nl/artikel/...",
"snippet": "De Amsterdamse software scale-up heeft een Serie A ronde van 12 miljoen euro afgesloten...",
"published_at": "2026-08-20T07:42:00Z",
"ingested_at": "2026-08-20T08:15:00Z",
"authors": [
{ "id": "aut_8f21c4", "name": "Joris de Vries" }
],
"outlet": {
"name": "Example Zakelijk",
"domain": "example.nl"
},
"language": "nl",
"country": "NL"
}
]
}
<?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>
What teams use the News API for
- Media monitoring and PR tools
- Track every mention of a brand, person or topic, including the regional and trade media that global APIs miss.
- Market and competitive intelligence
- Follow funding rounds, product launches, board changes and sector news in the Benelux the moment they happen.
- Research and data science
- Analyse and classify Dutch and French news metadata. Model training and fine-tuning require express written permission and the necessary third-party rights; they are not included by default.
- News aggregators and newsletters
- Feed a local or sector-specific feed without building your own crawler for hundreds of sources.
- Compliance and risk
- Adverse media screening that does not stop at the national dailies.
We built this for ourselves first
Presscloud is a PR platform that 15,600+ companies use to reach journalists in the Benelux. To know where press releases land, we had to track where the news actually appears. Not the top 300 outlets. All of them.
That index now processes 11,200+ articles a day from 3,300+ sources, and it grows every week. The News API is that same index, opened up.
- Coverage keeps growing
- Every source we add for Presscloud is available in the API right away.
- Author data is first class
- We need it ourselves, so it is there.
- Nobody else has the incentive
- Global providers optimise for breadth across 150 countries. We optimise for depth in three.
Pick the package that fits your volume
You pay monthly, based on how many calls you make and how far back you want to search. Cancel any month.
Starter
Excl. VAT
- Up to 1.000 calls per month
- Search articles back 1 day
- 60 requests per minute
- 2 API keys
Growth
PopularExcl. VAT
- Up to 10.000 calls per month
- Search articles back 7 days
- 120 requests per minute
- 5 API keys
Scale
Excl. VAT
- Up to 50.000 calls per month
- Search articles back 30 days
- 300 requests per minute
- 10 API keys
Enterprise
Excl. VAT
- Custom volume, from 50,000 calls
- Search articles back as far as you need
- 600 requests per minute
- 25 API keys
Create an account and get 100 free calls. You get a key right away, no credit card.
Request API access
We reply to every request within two working days.
- A sample dataset of 1,000 recent articles
- A proposal based on your volume and endpoints
- Direct contact with the team that builds the index
Thanks!
You will hear from us within two working days. In the meantime, take a look at the field reference and the sample response on this page.
Frequently asked questions
No. We deliver the title, snippet, URL and metadata. The full text stays with the publisher. That is how every major news API works, and it respects publishers' rights under Dutch and European law.
It differs per source: from a few minutes to around twelve hours after publication. For the occasional source it can take a little longer.
The Netherlands, Belgium (Dutch and French language media) and Luxembourg.
The author name as the outlet publishes it, as a field on the article. We do not return contact details.
How far back you can search depends on your package: 1 day on Starter, 7 days on Growth and 30 days on Scale. Full backfill is on Enterprise. Our index goes back to January 2015.
Yes, per plan. The limits come back in the response headers.
Yes. We process publicly published journalistic metadata. We do not return personal contact details, and authors can request removal via [email protected].