/handelsblatt/topics/articles

POST /api/handelsblatt/topics/articles

Price: 20 credits

List every Handelsblatt article filed under one topic, newest first: headline, kicker, lead text, publication and update times, authors, lead image with caption and photo credit and a subscriber-only flag. Reaches years back, far beyond the page count Handelsblatt itself advertises.

How to use it

Chronological archive of one Handelsblatt topic. topic takes the alias ('inflation', 'ukraine') or the full /themen/ URL. Entries carry id, article_title, kicker, lead_text, web_url, published_at, updated_at, authors, image, is_premium and content_type; feed id into handelsblatt/articles for the body. Ordering is strictly newest first, so a large count walks the topic backwards in time. Handelsblatt refuses to serve past the 10000th article of a topic, and that is the cap on count. The site's own page widget under-reports the archive by an order of magnitude and is ignored here.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• topic string required — Handelsblatt topic alias or its /themen/ URL (examples: "inflation", "kuenstliche-intelligenz", "https://www.handelsblatt.com/themen/ukraine"; minLength: 1)
• count integer required — Max number of articles to return (min: 1; max: 10000)

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 — Not a Handelsblatt topic alias or /themen/ URL, or count out of range Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit 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 — Handelsblatt has no topic page at this alias 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 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 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 Wait at least 30 seconds, then retry.

Response 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.