Croatian news API
Query Hrvatski coverage by keyword, meaning or both. Written in Latin . Pass hrv as the language filter.
What the coverage looks like
A smaller stream whose subject matter overlaps substantially with Serbian and Bosnian coverage while differing in framing. Tourism and EU affairs occupy proportionally more space than in neighbouring languages, reflecting where the economy sits.
| Articles observed | 677 |
|---|---|
| Distinct outlets | 48 |
| Articles per outlet | 14 |
| ISO-639-3 code | hrv |
| Script | Latin |
Outlet spread is the number worth watching here, not volume. 48 distinct publishers at roughly 14 articles each describes a very different information environment than the same total produced by a handful of prolific sources — and it is the difference between reaching independent reporting and reading one newsroom repeatedly.
In this sample the most active publisher is index.hr, carrying
about 36% of Croatian articles on its own, and the three busiest
— index.hr, vecernji.hr, net.hr — account for roughly 51% between
them. That is a concentrated distribution, so a query returning a lot of Croatian results may be reaching fewer independent newsrooms than the count implies. Scope by outlet if you need breadth rather than volume.
Script and matching behaviour
Latin script with diacritics that are frequently dropped in headlines and URLs. Rich case inflection. Vocabulary differs from Serbian in deliberate and politically meaningful ways, so a term common in one may be rare in the other despite mutual intelligibility.
How to query it
Do not assume Serbian and Croatian queries are interchangeable even though a speaker of one understands the other — the vocabulary differences are exactly the words a query is built from. Query both when your interest is regional.
Bound every request with a time range regardless of mode. Meaning-based retrieval always returns its best guesses, so an unbounded query produces a confident-looking result set anchored to nothing in particular. If results feed a model rather than a person, collapse to stories as well — one event covered by thirty outlets should cost you one item, not thirty.
Recent headlines in Hrvatski
Pulled from the index on 2026-07-31, shown in their original script so you can see what the API actually returns rather than a translated approximation of it.
Outlets publishing in Croatian
The most active publishers in this language, by article count. Use these as an outlet filter when you want to pin a particular market or editorial position rather than taking the whole language.
index.hr · vecernji.hr · net.hr · jutarnji.hr · 24sata.hr · naslovi.net · dnevnik.hr · avaz.ba · glas-slavonije.hr · novilist.hr · poslovni.hr · tportal.hr
What catches people out
Assuming Croatian and Serbian queries are interchangeable because speakers understand each other is the trap. The vocabulary differences are deliberate and politically meaningful, and they fall precisely on the words a query is built from, so intelligibility to a human says nothing about whether a matcher will find anything.
A worked case
Query both when your interest is regional, and expect the results to differ in framing rather than in subject. For tourism and EU accession coverage, this stream carries detail that regional reporting in other languages compresses into a sentence.
Where this language leads
Good on tourism, EU accession and regional politics. Business coverage is limited to a small set of outlets. Coverage of the Adriatic coast — tourism volumes, port activity, seasonal employment and the property market that follows them — is unusually detailed here, because those subjects carry disproportionate economic weight and the domestic press treats them as front-page material rather than as trade news.
Who queries it, and why
Queried for tourism, EU affairs and regional politics, often alongside Serbian and Bosnian rather than instead of them. A regional question is almost never answered by one of these language facets alone.
Reading these numbers
These figures are provisional. They are measured from the public source the index is built from rather than from the index itself, because the query endpoint is not yet reachable from the build. They are the right order of magnitude and the outlets and headlines are real, but they should not be quoted as coverage guarantees until a snapshot taken against the API replaces them.
A page exists for this language because the index carries enough Croatian coverage from enough distinct outlets to answer a real question about it. Languages that do not clear that bar deliberately have no page rather than a page that implies coverage which is not there.