/elpais/sections/articles

POST /api/elpais/sections/articles

Price: 5 credits

List the articles El Pais is currently showing on a section front, in the order the newsroom placed them. Returns headline, standfirst, publication time, byline and linked authors, kicker, thumbnail, the body word count El Pais publishes and its subscription badge.

How to use it

Read the current front page of an El Pais section. section is the path used in the site URL ('espana', 'economia', 'espana/madrid', 'deportes/futbol'), a full section URL, an 'en/' prefixed path for english.elpais.com or a 'cd/' prefixed one for Cinco Dias. This surface is the curated front, not an archive: El Pais serves no further pages for it, so a section front yields roughly 19 to 58 entries and count cannot reach beyond what is on the page today. Fronts also carry the opinion pieces the newsroom pinned to the section, and the business fronts carry Cinco Dias articles, so publication and section vary within one response. To page deep into a section's back catalogue use elpais/topics/articles with the same slug, or elpais/archives/articles day by day with the section filter. Each entry carries id, article_title, description, web_url, published_at, language, publication, content_type, section, kicker, byline, authors, dateline, has_subscription_badge, has_video, word_count and image; content_type is article for ordinary stories and series for the evergreen TV-series pages El Pais mixes into its television fronts, which elpais/articles does not resolve. word_count and the badge are printed on modern Spanish cards only, and elpais/articles holds the authoritative subscription tier. Feed id or web_url into elpais/articles for the body.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• section string required — El Pais section path, or the URL of the section front; prefix with en/ for the English edition or cd/ for Cinco Dias (examples: "espana", "espana/madrid", "https://elpais.com/economia/", "en/usa", "cd/companias"; minLength: 1)
• count integer required — Max number of articles to return (min: 1)

Response

• @type string (default: "ElpaisArticleCard")
• id string required
• article_title string required
• description string nullable
• web_url string required
• published_at integer nullable
• language string required
• publication string required
• content_type string required
• section string required
• kicker string nullable
• kicker_url string nullable
• byline string nullable
• authors array (default: [])
  • @type string (default: "ElpaisAuthorRef")
  • name string required
  • alias string nullable
  • profile_url string nullable
  • bio string nullable
  • image string nullable
• dateline string nullable
• has_subscription_badge boolean (default: false)
• has_video boolean (default: false)
• word_count integer nullable
• image string nullable

Errors

• 422 — Not an El Pais section path or section URL 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 El Pais section front at this 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.