/semafor/articles

POST /api/semafor/articles

Price: 5 credits

Get a full Semafor article by URL: headline, standfirst, the Semaform section blocks with their own headings and cited sources, the whole body as plain text and as HTML, publish and update timestamps, the credited reporters with their profile links, the vertical the piece is filed under, the lead image with its photo credit and the newsletter the story was written for.

How to use it

Fetch one Semafor article. Accepts the article URL (https://www.semafor.com/article/MM/DD/YYYY/slug) or the bare MM/DD/YYYY/slug path. Returns one item with article_title, description, text, html, sections[] (each with heading, text, html and sources[] — this is the Semaform structure: The News, the reporter's view, Room for Disagreement, The View From, Notable), published_at and updated_at, published_on, authors[], section, image and image_credit, newsletter and template. Use semafor/verticals/articles to discover article URLs.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• article string required — Semafor article URL or its MM/DD/YYYY/slug path (examples: "https://www.semafor.com/article/08/05/2026/anthropic-openai-models-attempt-to-fool-humans", "08/05/2026/anthropic-openai-models-attempt-to-fool-humans"; minLength: 1)

Response

• @type string (default: "SemaforArticle")
• alias string required
• article_title string required
• web_url string required
• template string required
• published_on string nullable
• published_at integer nullable
• updated_at integer nullable
• description string nullable
• social_title string nullable
• section string nullable
• section_name string nullable
• section_url string nullable
• image string nullable
• image_credit string nullable
• text string nullable
• html string nullable
• authors array (default: [])
  • @type string (default: "SemaforAuthor")
  • name string required
  • alias string nullable
  • profile_url string nullable
• sections array (default: [])
  • @type string (default: "SemaforArticleSection")
  • heading string nullable
  • text string nullable
  • html string nullable
  • sources array (default: [])
• newsletter object nullable
  • @type string (default: "SemaforNewsletter")
  • name string nullable
  • alias string nullable
  • frequency string nullable
  • web_url string nullable

Errors

• 422 — The request body did not validate 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 — Article not found (well-formed but nonexistent Semafor article URL or path) 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.