Portuguese news API
Query Português coverage by keyword, meaning or both. Written in Latin . Pass por as the language filter.
What the coverage looks like
Two distinct centres — Brazil and Portugal — with different orthographic conventions, different news cycles and very different scale. Brazilian coverage dominates volume, so a query without an outlet constraint is effectively a Brazilian query with a small European tail.
| Articles observed | 1.1k |
|---|---|
| Distinct outlets | 100 |
| Articles per outlet | 11 |
| ISO-639-3 code | por |
| Script | Latin |
Outlet spread is the number worth watching here, not volume. 100 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 globo.com, carrying
about 16% of Portuguese articles on its own, and the three busiest
— globo.com, sapo.pt, uol.com.br — 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
Orthography diverges between the two variants even after reform, and accent usage differs. Inflection is rich, and Brazilian headline style is noticeably more colloquial than European, which widens the vocabulary gap between newsrooms describing the same event.
How to query it
Decide which of the two markets you want and scope by outlet accordingly; the default of "all Portuguese" is rarely what anyone intends. Semantic mode bridges the orthographic split, which keyword matching handles badly.
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 Português
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 Portuguese
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.
globo.com · sapo.pt · uol.com.br · brasil247.com · otempo.com.br · jornaleconomico.sapo.pt · rondoniadireta.com · jornaldebrasilia.com.br · correiobraziliense.com.br · observador.pt · ig.com.br · em.com.br
What catches people out
Assuming the two variants are interchangeable is the usual error. Brazilian and European Portuguese differ in orthography, vocabulary and register, and Brazilian volume is large enough that an unscoped query is effectively a Brazilian query. Teams building for a European Portuguese audience frequently discover this only after users complain the feed feels foreign.
A worked case
Scope by outlet to pick a market before anything else, then use semantic mode so the orthographic differences do not cost you matches within it. For commodity and agribusiness coverage, the Brazilian press is the primary source and is considerably more detailed than international reporting on the same harvests, shipments and export figures.
Where this language leads
Deep on Brazilian politics, agribusiness and energy, and on Lusophone African affairs that are barely covered elsewhere. Technology coverage is concentrated in a small number of outlets.
Who queries it, and why
Queried overwhelmingly for Brazil — agribusiness, commodities, energy and politics — with a much smaller European Portuguese use case that is easy to swamp accidentally. Lusophone African coverage is a third audience, small but almost unserved elsewhere.
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 Portuguese 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.