> **For coding agents and LLMs:** This is one Social Fetch marketing page (markdown export). For API orientation start with [`/llms.txt`](https://www.socialfetch.dev/llms.txt); for auth and crawl rules use [`/agents.txt`](https://www.socialfetch.dev/agents.txt); for every operation use [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt). ## This page - **On-site (HTML):** - **Markdown (.mdx) URL:** --- # Google News Sections API An edition's navigation sections and the topic ids the other routes take. `GET /v1/google-news/sections` returns `edition` and `sections`. Each section has an `id` and a `name` in the edition's language, in Google News order. The id is the same topic id that `GET /v1/google-news/topics/{topicId}` accepts. This is reference data: it changes rarely, so the answer is cached for a day. Use it to build a section picker, then get a section's articles with the topic route. The home route also returns this list alongside its briefing. ## Request - **Endpoint:** `GET /v1/google-news/sections` - **Credits:** 1 credit Failed requests are free - **Input:** by edition - **Full reference:** [docs](https://www.socialfetch.dev/docs/api/v1/google-news/sections/get) - **Platform page:** [/platforms/google-news](https://www.socialfetch.dev/platforms/google-news) ## FAQ ### What is a section id? It is a topic id. Pass it to `GET /v1/google-news/topics/{topicId}` to read that section's articles. ### Why is the list cached? Edition navigation changes rarely, so the route caches it for a day. A cached answer still carries the normal `{ data, meta }` envelope. ### Does every edition have the same sections? No. Each edition has its own sections for that language and country. The names are in the edition's language. ### How many credits does it cost? Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged: that field is the billing source of truth.