Serbian news API
Query Српски / Srpski coverage by keyword, meaning or both. Written in Cyrillic and Latin . Pass srp as the language filter.
What the coverage looks like
Unusual among major languages in being written in two scripts, often by the same publisher, sometimes within one site. This is the fact most likely to silently halve your results.
| Articles observed | 1.1k |
|---|---|
| Distinct outlets | 51 |
| Articles per outlet | 22 |
| ISO-639-3 code | srp |
| Script | Cyrillic and Latin |
Outlet spread is the number worth watching here, not volume. 51 distinct publishers at roughly 22 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 naslovi.net, carrying
about 23% of Serbian articles on its own, and the three busiest
— naslovi.net, b92.net, blic.rs — account for roughly 43% between
them. That is a concentrated distribution, so a query returning a lot of Serbian 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
Cyrillic and Latin are both standard and fully interchangeable, and a keyword query in one script matches nothing written in the other. Mutual intelligibility with Croatian and Bosnian also means related coverage sits in adjacent language facets.
How to query it
Never rely on a single-script keyword query. Semantic mode handles the split; if you must use keyword mode, query both scripts and merge. Consider querying Croatian alongside Serbian when your interest is regional rather than national.
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 Српски / Srpski
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 Serbian
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.
naslovi.net · b92.net · blic.rs · politika.rs · informer.rs · telegraf.rs · danas.rs · tanjug.rs · novosti.rs · alo.rs · rts.rs · rtrs.tv
What catches people out
The two-script problem is the one that silently halves result sets. Cyrillic and Latin are both fully standard, sometimes on the same site, and a keyword query in one matches nothing written in the other. A team can run this for months believing coverage is thin when they are seeing roughly half of it.
A worked case
Never rely on a single-script keyword query. Semantic mode handles the split; if keyword mode is unavoidable, query both scripts and merge the results. When your interest is regional rather than national, query Croatian alongside Serbian, since mutually intelligible coverage is split across separate language facets.
Where this language leads
Strong on regional politics, and on Balkan affairs generally where coverage in any other language is thin and usually second-hand.
Who queries it, and why
Queried for Balkan regional politics, where coverage in other languages is thin and usually second-hand. The dual-script issue means teams routinely see half of what exists and conclude the coverage is sparse.
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 Serbian 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.