api-version header using dated versions (YYYY-MM-DD). Versions are backward-compatible snapshots of the API contract.
Selecting a version
Send theapi-version header with the version you want:
Current version
The latest version is2026-08-01. It includes search, publishers, article content, random articles, trending topics, and info endpoints. In this version:
- Responses use a snake_case envelope with
metadata,parameters,pagination, and resource-named keys. - Articles expose a stable
id(when your plan includes it) andtranslationsfor non-English articles. GET /articleaccepts exactly one ofidorurl.
Legacy versions
Older versions remain available for existing integrations:2024-01-01: uses a camelCase envelope (success,size,totalHits, …) and does not expose articleidortranslations.2022-01-01: legacysearchandtop-headlinescontracts.
New fields are only available in the version where they were introduced. Requesting a route that doesn’t exist in your selected version returns a
404.Upgrading
To upgrade to the latest version:- Switch the
api-versionheader to2026-08-01in a staging environment. - Review the response shape: results are now wrapped in a
metadata/parameters/paginationenvelope with snake_case field names and resource-named keys (articles,article,publishers,topics,countries,languages). - Handle the new
idandtranslationsfields on articles where your plan exposes them. - Update your code and roll out.