Web and news · Serper

news.search

Searches the news index with article titles, publisher names, dates and source links. Cached detail is the indexed metadata; read the publisher page separately for its full text.

Operation: POST /v1/capabilities/news.search/execute
operationId: executeNewsSearch
Typical credits: 1
Search deadline: 15 s server-side
Paging: page
Availability: ConfiguredChecked 2026-09-23 21:02 UTC

Cost basis: $0.001 per provider-reported credit, including the full fetched page. Availability is reported per deployment by GET /v1/catalog (available). The timestamped snapshot describes configuration, not provider uptime or your account's enabled choices. Check the catalog with your own key before a call. Credits are explained under credits and limits.

Request

Body of POST /v1/capabilities/news.search/execute, JSON, validated against the NewsSearchRequest component of the public OpenAPI document. Defaults are applied server-side, so an omitted optional field behaves exactly as its default.

Request fields of news.search
Field	Type	Required	Default	Constraints and description
query	string	yes		min length 1, max length 500
country	string	no		pattern ^[a-zA-Z]{2}$
language	string	no		pattern ^[a-zA-Z]{2,3}(-[a-zA-Z]{2})?$
time_range	"day" \| "week" \| "month" \| "year"	no
num	integer	no	10	min 1, max 20

Unknown keys are rejected with 400 invalid_request.

Examples

Latest reporting

curl

curl -s -X POST https://api.powerups-ai.store/v1/capabilities/news.search/execute \
  -H "Authorization: Bearer $AIPA_API_KEY" -H "Content-Type: application/json" \
  -d '{"query":"renewable energy","num":5}'

No recorded response is published for this capability yet. The envelope is the ExecuteResponse component (see sessions and records); the record keys below are what the adapter emits. A first call with the example above returns search_id, the records and the charge.

Result record

Every item in results[] carries record_id and title (contract, always present) and usually url and snippet. The keys below are the documented tier: produced deterministically by this capability, omitted when the source has no value, checked against recorded source fixtures in our test suite, and published as the NewsSearchRecord component (all optional, extra keys allowed) so generated clients type them. The wire schema itself still validates only the base keys. See stability tiers.

Record keys of news.search
Key	Type	Presence
publisher	string	when the source has it
published_label	string	when the source has it
image_url	string	when the source has it
source	string	always
fetched_at	string	always
content_scope	string	always

Caveats

Details are served from the record stored at search time without a provider call. When that stored detail is no longer available the call returns 410 session_expired ("the cached record detail is no longer available. Run the search again."); it is never re-fetched.

Follow-ups

Paging: Provider page number; more fetches the next page from the source. Send { "search_id": "…", "action": "more" } while has_more is true; tolerate an empty page and stop after a bounded number of pages.
Update: Re-run with changed parameters (merged into the stored query); page state resets, search_id stays. Params accept any subset of the request fields (NewsSearchUpdateParams).
Record actions:
- details: Cached article metadata and original source link.
Detail behaviour: Stored at search time; details is free and never calls the provider. details returns the article record stored at search time at no charge.

record action

curl -s -X POST https://api.powerups-ai.store/v1/follow-up \
  -H "Authorization: Bearer $AIPA_API_KEY" -H "Content-Type: application/json" \
  -d '{"record_id":"rec_…","action":"details"}'

Record detail objects of this capability are provider-shaped: documented by observation, not by schema. Full follow-up semantics: follow-up.

Typed client

With types generated from the public document (see types, client and samples) the call is path-keyed and the body is checked at compile time:

TypeScript (openapi-fetch)

const { data, error } = await client.POST("/v1/capabilities/news.search/execute", {
  body: {
    "query": "renewable energy",
    "num": 5
  },
});
if (error) throw new Error(`${error.error.code}: ${error.error.message}`);
for (const record of data.results) console.log(record.record_id, record.title);