Turkish news API

What the coverage looks like

A large domestic press with high publication frequency and substantial syndication between outlet groups. Coverage of the surrounding region is extensive and often earlier than Western reporting on the same events.

Outlet spread is the number worth watching here, not volume. 126 distinct publishers at roughly 27 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 haberler.com, carrying about 18% of Turkish articles on its own, and the three busiest — haberler.com, birgun.net, haberport.com — account for roughly 26% 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

Agglutinative: a single Turkish word can carry what English expresses in a whole clause, with suffixes stacking to encode possession, case, negation and tense. The surface forms a stem generates are effectively unbounded, which makes exact matching close to useless. Dotted and dotless i are distinct letters and are frequently confused.

How to query it

Semantic mode is not optional here — it is the only mode that works reliably. Do not construct keyword queries from dictionary forms; they will match a small and unrepresentative slice of the coverage.

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 Türkçe

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 Turkish

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.

haberler.com · birgun.net · haberport.com · sabah.com.tr · mersinhaber.com · bursadabugun.com · dunya.com · ensonhaber.com · haber7.com · haberturk.com · sozcu.com.tr · aa.com.tr

What catches people out

Agglutination defeats keyword matching more completely here than almost anywhere else. A single word can carry what English needs a clause for, and the number of surface forms a stem generates is effectively unbounded. Dictionary-form queries return a small and unrepresentative slice, and the dotted and dotless i are distinct letters that are frequently confused in both queries and source text.

A worked case

Semantic mode is the only reliable option — treat keyword mode as unavailable rather than as a fallback. For energy corridor and construction stories, Turkish coverage often precedes Western reporting on the same projects, and querying it directly is the difference between finding out now and finding out later.

Where this language leads

Strong on regional politics, energy corridors and construction, with substantial coverage of Central Asia, the Caucasus and the Middle East.

Who queries it, and why

Queried for energy corridors, construction and regional politics spanning the Caucasus, Central Asia and the Middle East. Turkish coverage of those regions frequently precedes Western reporting, which is the main reason to take on the tokenisation difficulty.

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 Turkish 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.