Familiar with v1 or v2? The date-based versions map to: v1 =
2022-01-01, v2 = 2024-01-01, v3 = 2026-05-25. See the migration guide for upgrade steps.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-05-25. It includes search, topics, frontpage, stories, publications, and retrieve endpoints.
Legacy versions
Two older versions remain available for existing integrations:2024-01-01: legacy search and topic-headlines contracts.2022-01-01: the original search contract.
New endpoints are only available in the version where they were introduced. Requesting a route that doesn’t exist in your selected version returns a
404.API Reference by version
Use the version selector in the API Reference sidebar to switch between versions. Each version shows the endpoints and response shapes available in that version.Response shape differences
The key difference between versions is the response envelope. Version2024-01-01 and earlier use a flat camelCase envelope:
2026-05-25 uses a structured snake_case envelope:
Upgrading from 2024-01-01 to 2026-05-25
- Switch the
api-versionheader to2026-05-25in a staging environment. - Update response parsing: results are now wrapped in
metadata/parameters/news_articlesinstead of flatsuccess/size/totalHits. - Handle the new
typediscriminator onnews_articlesitems (articles, stories, storylines, social posts). - Update error handling: errors now use the
metadata+errorsenvelope instead of{ success: false, code, message, fields }. - Test and roll out.