POST /api/spiegel/articles
Price: 10 credits
Get one Der Spiegel article by its URL or uuid: headline, standfirst, body text, publication, creation and update times, bylined authors, section, keywords, lead image with caption and photo credit, in-body images, pull quotes and related links. Works for the German site and for Spiegel International in English. SPIEGEL+ articles are hard-gated: an anonymous client gets the full metadata and no body at all, and is_truncated says so.
Fetch one Der Spiegel article. article takes the full URL or just the id that ends it. Spiegel has three id spaces and all resolve: the uuid on modern articles (3d48792f-715a-4fb7-89c4-ecab8b1c475a), the legacy number on archive articles whose URL ends -a-393044.html, and the number on photo galleries whose URL ends -fotostrecke-122824.html. A wrong slug or section in the URL still lands on the right article, and the uuid the search endpoint returns for an archive article or a gallery resolves to its numeric URL. id echoes the form you passed; canonical_id is the id in the article's own canonical URL. Returns article_title, heading (the part before the colon), description, text, published_at/created_at/updated_at (unix), language (de or en), authors and byline, section, sections (breadcrumb), keywords, image with image_caption and image_credit, images, quotes, video_url on video pages and related_articles. content_type is article, video or gallery, and a gallery returns every slide in images with its caption and photo credit but no body text. is_premium marks SPIEGEL+ and is_truncated repeats it: an anonymous client never receives the whole body of a subscriber-only article. On the German site those carry no body at all (text null, paragraph_count 0); on Spiegel International they carry a short opening extract of a few paragraphs. Use spiegel/articles/search or spiegel/feeds to find ids.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)article string required — Der Spiegel article URL, the article uuid, or the legacy numeric id of an archive article (examples: "https://www.spiegel.de/wissenschaft/mensch/dr-kongo-mehr-als-4000-menschen-mit-ebola-infiziert-a-3d48792f-715a-4fb7-89c4-ecab8b1c475a", "3d48792f-715a-4fb7-89c4-ecab8b1c475a", "https://www.spiegel.de/politik/ausland/gasstreit-schwelt-weiter-a-393044.html", "393044"; minLength: 1)@type string (default: "SpiegelArticle")id string requiredcanonical_id string nullablearticle_title string requiredheading string nullabledescription string nullabletext string nullableweb_url string requiredpublished_at integer nullablecreated_at integer nullableupdated_at integer nullablelanguage string requiredcontent_type string requiredsection string nullablesections array (default: [])@type string (default: "SpiegelTerm")name string requiredweb_url string nullablekeywords array (default: [])byline string nullableauthors array (default: [])publisher string nullableimage string nullableimage_caption string nullableimage_credit string nullableimages array (default: [])@type string (default: "SpiegelImage")image string requiredcaption string nullablecredit string nullablealt string nullablequotes array (default: [])video_url string nullablevideo_duration string nullableis_premium boolean (default: false)is_truncated boolean (default: false)paragraph_count integer (default: 0)related_articles array (default: [])@type string (default: "SpiegelRelatedArticle")id string requiredarticle_title string requiredweb_url string required422 — Not a Der Spiegel article URL, uuid or legacy numeric id 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 — No Der Spiegel article with this id, or the id resolves to another Spiegel-Group masthead 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.