# /handelsblatt/articles/search

`POST /api/handelsblatt/articles/search`

Price: 10 credits

Search Handelsblatt by keyword. Returns listing entries with headline, kicker, lead text, publication and update times, authors, lead image with caption and photo credit, a subscriber-only flag and, for podcast episodes, the audio file and its duration. Newest first.

## How to use it

Keyword search across Handelsblatt, ordered newest first. Each entry carries id, article_title, kicker, lead_text, web_url, published_at, updated_at, authors, image, is_premium and content_type (article, comment, longread or podcast — the same editorial-format vocabulary handelsblatt/articles reports; a cover story only resolves to that fifth value once fetched, it lists here as longread). Feed id or web_url into handelsblatt/articles for the body. count has no ceiling: results run out where Handelsblatt's own set of matches ends. What bounds a very large pull is time rather than any limit — a few thousand articles is the practical reach of one request, and the broadest German stop words, which match around 22,000 articles, will not finish inside one even at the maximum timeout. Results always begin at the newest article, so a narrower keyword is the only way to reach older ones. Matching is loose — a term that appears nowhere still returns a handful of rows — so check the returned headlines. keyword is the only filter the surface has: Handelsblatt accepts section, author, doctype, sort and date parameters and measurably ignores every one of them. The index covers roughly the last twelve months; for anything older use handelsblatt/topics/articles, which walks a topic back years.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `keyword` (string, required) — Search phrase (examples: "Inflation", "Künstliche Intelligenz"; minLength: 1)
- `count` (integer, required) — Max number of results to return (min: 1)

## Response

### 200 — Successful Response

- `@type` (string) (default: "HandelsblattTeaser")
- `id` (string, required)
- `article_title` (string, required)
- `kicker` (string, nullable)
- `lead_text` (string, nullable)
- `web_url` (string, required)
- `published_at` (integer, nullable)
- `updated_at` (integer, nullable)
- `content_type` (string, required)
- `label` (string, nullable)
- `access_category` (string, nullable)
- `is_premium` (boolean) (default: false)
- `authors` (array) (default: [])
  - `@type` (string) (default: "HandelsblattAuthor")
  - `id` (string, required)
  - `name` (string, required)
  - `first_name` (string, nullable)
  - `last_name` (string, nullable)
  - `initials` (string, nullable)
  - `profile_url` (string, nullable)
  - `image` (string, nullable)
- `image` (object, nullable)
  - `@type` (string) (default: "HandelsblattImage")
  - `id` (string, required)
  - `image` (string, required)
  - `caption` (string, nullable)
  - `credits` (string, nullable)
  - `alt` (string, nullable)
  - `orientation` (string, nullable)
  - `aspect_ratio` (number, nullable)
- `podcast` (object, nullable)
  - `@type` (string) (default: "HandelsblattPodcast")
  - `id` (string, nullable)
  - `audio_url` (string, nullable)
  - `duration` (integer, nullable)
  - `episode` (integer, nullable)

## Errors

### 422 — Validation Error

Blank keyword, or count below 1

What to do: Check the fields against this schema. A URN with the wrong prefix is the most common cause.

- `detail` (array)
  - `loc` (array, required)
  - `msg` (string, required)
  - `type` (string, required)
  - `input` (any)
  - `ctx` (object)

### 408

The request ran past its time limit

What to do: Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.

### 412

The entity was not found, or a precondition failed

What to do: Retrying will not help: either the entity does not exist, or the input points at a different one.

### 429

Too many requests: a rate limit or a usage window is exhausted

What to do: When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.

### 500

Something broke on our side

What to do: Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.

### 529

Rate limit reached, or the endpoint is overloaded

What to do: Wait at least 30 seconds, then retry.

## Response envelope

Success: Array of objects (may be empty if no results)

Error: Error may coexist with partial results if it occurs mid-execution. Check X-Error header and status code.

Every response carries these headers:

- `X-Error` — Error message text (present only on error)
- `X-Request-ID` — Unique request identifier
- `X-Execution-Time` — Execution time in seconds
- `X-Result-Count` — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
- `X-Total-Available-Results` — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
- `X-Warning` — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
- `X-Retry-After` — Seconds to wait before retrying. Present only on 429.