/semafor/verticals/articles

POST /api/semafor/verticals/articles

Price: 5 credits

List the articles currently on a Semafor vertical front — Politics, Business, Technology, Energy, Gulf, China, Africa, Security, Media or CEO Signal. Each card carries the headline, the standfirst, the publication date, the article URL and the lead photo credit.

How to use it

List the articles on one Semafor vertical front. vertical takes the slug (politics, business, tech, energy, gulf, china, africa, security, media, ceo) or the full /vertical/{slug} URL, and count says how many articles to return. Each item has article_title, excerpt, web_url, alias, published_on and image_credit. Pass web_url to semafor/articles for the full Semaform body. The front carries only the current articles; it does not page back into the archive.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• vertical string required — Semafor vertical slug or its section URL (examples: "politics", "https://www.semafor.com/vertical/tech"; minLength: 1)
• count integer required — Max number of articles to return (min: 1)

Response

• @type string (default: "SemaforArticleCard")
• article_title string required
• web_url string required
• alias string required
• published_on string nullable
• excerpt string nullable
• image string nullable
• image_credit 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 — Vertical not found, or the vertical front carried no article cards 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.