Search Google News API

Endpoint facts

Method

GET

API path

/google/news

Auth

apiKey

Credits

3 credits/request

Platform

Google

Response schema

#/definitions/google.newsResponseDoc

MCP tool

google_news

Overview

Returns current Google News search results using anonymous HTTP requests with fresh proxy profiles, without browser rendering. Pages slice the finite result snapshot; they do not traverse the Google Search index. Results include title, source, publisher article URL, age, and thumbnail when available. Valid no-results searches and exhausted pages return an empty array. Locale defaults to country=us and lang=en. Returns 503 for blocked or malformed upstream responses. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost

3 credits/request

Charged response

Successful 2xx responses

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

• Proxy strategy: managed automatically where needed
• Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
• Browser cluster: supported dynamic workloads can be routed through distributed browser instances
• Retry behavior: automatic retry/fallback may be used depending on endpoint type
• Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
• Billing: credits are charged only for successful 2xx responses
• Observability: responses include request context where available

Browser cluster behavior

Some targets require real browser execution because the data is loaded through JavaScript, dynamic rendering, or interaction-like browser behavior.

For supported endpoints, Crawlora can route requests through a managed browser cluster. This allows Crawlora to execute JavaScript, load dynamic content, apply browser-level request behavior, and normalize the rendered result into JSON.

You do not need to operate your own Playwright, Puppeteer, Chrome, proxy, queue, or retry infrastructure.

Response behavior

- Pagination slices the current finite result snapshot, which typically contains about 100 articles. It does not page through the Google Search index or retrieve a historical archive. Narrow `q` to retrieve a more specific set of stories. - Result contents and ordering can change between requests. Pages are not a persistent snapshot. - Positions are 1-based across the snapshot. `next_page` appears only when another item exists; a full final page does not advertise another page. - Valid no-results searches and pages beyond the end return `results: []` without `next_page`. - Blocked, malformed, or unrecognizable upstream responses return `503`. - `url` links directly to the publisher. `thumbnail` is included when available. Article summaries are not supplied by this source, so `description` is omitted. `age` is relative to publication time. - Requests use an anonymous HTTP source with bounded fresh-proxy retries. No browser rendering or browser fallback is used. Example response: ```json { "code": 200, "msg": "OK", "data": { "results": [ { "position": 1, "title": "Example headline", "url": "https://example.com/news/story", "source": "Example News", "age": "2 hours ago" } ], "pagination": { "page": 1 } } } ```

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Related