Arabic news API

What the coverage looks like

Coverage spans the Gulf, the Levant and North Africa, with editorial positions that differ more sharply between publishers than in most language groups. Any sentiment figure computed across an unfixed outlet set describes which publishers your query reached rather than anything about the story.

Outlet spread is the number worth watching here, not volume. 94 distinct publishers at roughly 10 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 dostor.org, carrying about 16% of Arabic articles on its own, and the three busiest — dostor.org, vetogate.com, shorouknews.com — account for roughly 34% 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

Written right to left, usually without the short vowel diacritics that would disambiguate related forms. Morphology is templatic: one root generates dozens of surface words by inserting vowel patterns, and the definite article attaches directly to the noun, so prefix matching produces both false positives and false negatives.

How to query it

Semantic mode strongly preferred. If you render results in a left-to-right layout, set direction per result or punctuation appears on the wrong side of every headline. Fix your outlet set before comparing sentiment over time.

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 Arabic

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.

dostor.org · vetogate.com · shorouknews.com · eremnews.com · nile.eg · almasryalyoum.com · aljazeera.net · ahram.org.eg · bokra.net · libyaakhbar.com · euronews.com · cnn.com

What catches people out

Sentiment is the specific hazard. Editorial stance varies enormously between publishers covering the same event, so an average across whichever outlets a query reached describes the publisher mix rather than any property of the story. This is true to a degree everywhere and is more pronounced here than in any other major language.

A worked case

Fix the outlet set, then compare within it over time. Render results with direction set per item — mixing right-to-left headlines into a left-to-right layout without marking direction puts punctuation on the wrong side of every line, which looks like a data problem and is a display one.

Where this language leads

Deep on regional diplomacy, energy markets and security. Technology and consumer coverage is comparatively thin, so widen the window rather than loosening the query in those areas.

Who queries it, and why

Queried for regional diplomacy, energy and security by teams that need the reporting rather than the commentary about it. The editorial spread means an unscoped query produces an average of incompatible positions, which is worse than useless for analysis.

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