Ukrainian news API
Query Українська coverage by keyword, meaning or both. Written in Cyrillic . Pass ukr as the language filter.
What the coverage looks like
A stream that grew rapidly and is heavily weighted towards domestic affairs, regional administration and security. Notably, many outlets publish in both Ukrainian and Russian, so the same newsroom can appear in two language facets with partly overlapping content. Volume is concentrated in domestic subjects to an unusual degree, with comparatively little coverage of events elsewhere unless they bear directly on the country. That focus is what makes the stream valuable — the depth on domestic matters is extraordinary — but it also means it is a poor general-purpose news source, and pairing it with another language is usually necessary for anything with an international dimension.
| Articles observed | 1.3k |
|---|---|
| Distinct outlets | 118 |
| Articles per outlet | 11 |
| ISO-639-3 code | ukr |
| Script | Cyrillic |
Outlet spread is the number worth watching here, not volume. 118 distinct publishers at roughly 11 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 obozrevatel.com, carrying
about 5% of Ukrainian articles on its own, and the three busiest
— obozrevatel.com, glavcom.ua, tsn.ua — account for roughly 14% between
them. That is a comparatively flat distribution, which means volume here translates fairly directly into independent reporting rather than one newsroom publishing repeatedly.
Script and matching behaviour
Cyrillic, but with letters that Russian does not use and different values for some shared characters, so Russian-language queries do not transfer cleanly. Seven cases with vocative, and the same flexible word order that makes phrase matching unreliable.
How to query it
Query in Ukrainian rather than assuming Russian coverage substitutes for it — the two facets carry different material even from the same publishers. Semantic mode for anything beyond a proper noun.
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 Українська
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 Ukrainian
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.
obozrevatel.com · glavcom.ua · tsn.ua · 24tv.ua · unian.ua · korrespondent.net · interfax.com.ua · unn.ua · ukrinform.ua · liga.net · zn.ua · lb.ua
What catches people out
The overlooked fact is that many outlets publish in both Ukrainian and Russian, so the same newsroom appears in two language facets with partly different content. Querying only one and assuming it covers that publisher's output is a systematic and invisible omission.
A worked case
Query Ukrainian explicitly rather than assuming Russian-language coverage substitutes for it. For regional administration and infrastructure reporting, the level of local detail available here has no equivalent in any other language, and it is frequently the only source for what is happening outside the largest cities.
Where this language leads
Very strong on regional administration, infrastructure and security reporting at a level of local detail that has no English-language equivalent. Reconstruction and energy-grid coverage is similarly granular — individual substations, specific repair timelines, named contractors — the kind of operational specificity that international reporting compresses into a single sentence about damage to infrastructure, when it mentions it at all.
Who queries it, and why
Queried for security, regional administration and reconstruction. The local granularity is the value: what is happening in a specific oblast is reported here and essentially nowhere else, and the level of operational detail is unmatched.
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 Ukrainian 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.