Getting Google News data programmatically
Google News is the fastest-moving public dataset most teams never capture. There’s no official results API — the RSS feeds are thin, lack clustering, and don’t match what a user in a given country actually sees. If news coverage matters to you — PR, comms, risk, trading — you need the real surface as data.
The endpoint
curl -X POST https://api.answerline.dev/v1/monitor/google/news \
-H "Authorization: Bearer $API_KEY" \
-H "Content-Type: application/json" \
-d '{ "prompt": "acme corp", "country": "DE", "device": "DESKTOP" }'The response returns the result types the page actually shows: headline stories, story clusters, “Beyond the front page” picks, “From the web” links — each with source name, timestamp and URL. Geo and device parameters are real: German news for a German user, not a US view with a flag.
What people build on it
- PR & comms: alert when your brand (or a competitor’s) enters a news cluster; measure pickup velocity, not just mentions.
- Adverse media screening: scheduled queries per entity per market — see the adverse media use case.
- Editorial intelligence: which outlets get clustered together, which stories get “Beyond the front page” — a live map of what News thinks matters.
- Content timing: watch when a topic starts clustering, publish into the wave.
Polling vs events
News moves fast; schedule polling per topic rather than waiting on a single check. A task queue with 15–60 minute intervals per keyword is the usual shape — async tasks make that one batch call on a cron.
For the full field list, see the Google News engine page and news monitoring use case.