/theverge/articles

POST /api/theverge/articles

Price: 10 credits

Get a full The Verge story by id, URL or node id: headline, excerpt, the body as plain text and as HTML, separate first-publication, publication and update timestamps, word count, every credited author with job title and bio, the topic taxonomy with its parent chain, the storystreams the piece belongs to, the lede image with caption and photo credit, the live comment count and the SEO, social and promo headline variants. Works for all three kinds of Verge story: full articles, the short quick posts, and storystreams, which also list the pieces they collect.

How to use it

Fetch a single The Verge story. Accepts the numeric id that sits in the URL (https://www.theverge.com/{topic}/{id}/{slug} or the older /YYYY/M/D/{id}/{slug}), the full URL, or the base64 node id. Returns one item with article_title, alias (the story slug), excerpt, text (plain text body), html (reconstructed markup), published_at, first_published_at, updated_at and created_at as unix timestamps, word_count, comment_count, authors[] (name, job_title, short_bio, image), primary_category and categories[] (each with breadcrumbs of its parent topics), streams[] (the storystreams the piece belongs to), image plus image_alt/image_caption/image_credit, seo_headline/seo_description, social_headline/social_description, promo_headline, and, on quick posts, link_url/link_title/link_source for the external item being commented on. content_type is 'post' for a full article, 'quickPost' for a short one and 'stream' for a storystream, which also fills stream_articles[] with the pieces it collects and feed_url with its own RSS feed. id is the current WordPress id, the same numbering every other The Verge endpoint publishes; chorus_id and chorus_uuid are the ids the pre-2025 Vox platform used. On a /YYYY/M/D/{id}/{slug} or /{id}/{slug} URL the numeric segment is a third, legacy number that equals neither of them, so pass the URL or that number back as article rather than trying to match it against id or chorus_id. Use theverge/articles/search or theverge/categories/articles to discover ids.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• article string required — The Verge article id, article URL or Verge node id (examples: "979928", "https://www.theverge.com/tech/979928/cmf-clip-pro-review", "dmcyOnBvc3Q6OTc5OTI4"; minLength: 1)

Response

• @type string (default: "ThevergeArticle")
• id integer required
• node_id string required
• content_type string nullable
• article_title string required
• alias string nullable
• web_url string required
• path string nullable
• published_at integer nullable
• first_published_at integer nullable
• updated_at integer nullable
• created_at integer nullable
• excerpt string nullable
• word_count integer nullable
• comment_count integer nullable
• comments_enabled boolean (default: false)
• comments_mode string nullable
• chorus_id integer nullable
• chorus_uuid string nullable
• is_paywall_eligible boolean (default: false)
• has_affiliate_links boolean (default: false)
• is_live boolean (default: false)
• status string nullable
• image string nullable
• image_alt string nullable
• image_width integer nullable
• image_height integer nullable
• image_caption string nullable
• image_credit string nullable
• image_credit_hidden boolean (default: false)
• authors array (default: [])
  • @type string (default: "ThevergeAuthorBrief")
  • id integer nullable
  • node_id string required
  • name string required
  • alias string nullable
  • path string nullable
  • web_url string nullable
  • job_title string nullable
  • short_bio string nullable
  • image string nullable
• additional_bylines string nullable
• primary_category object nullable
  • @type string (default: "ThevergeCategory")
  • id integer nullable
  • node_id string required
  • name string required
  • alias string nullable
  • path string nullable
  • web_url string nullable
  • is_hub boolean (default: false)
  • breadcrumbs array (default: [])
    • @type string (default: "ThevergeCategoryRef")
    • node_id string required
    • name string required
    • alias string nullable
    • path string nullable
    • web_url string nullable
• categories array (default: [])
  • @type string (default: "ThevergeCategory")
  • id integer nullable
  • node_id string required
  • name string required
  • alias string nullable
  • path string nullable
  • web_url string nullable
  • is_hub boolean (default: false)
  • breadcrumbs array (default: [])
    • @type string (default: "ThevergeCategoryRef")
    • node_id string required
    • name string required
    • alias string nullable
    • path string nullable
    • web_url string nullable
• streams array (default: [])
  • @type string (default: "ThevergeStream")
  • id integer nullable
  • node_id string required
  • name string required
  • path string nullable
  • web_url string nullable
  • chorus_id integer nullable
  • is_live boolean (default: false)
• text string nullable
• html string nullable
• seo_headline string nullable
• seo_description string nullable
• social_headline string nullable
• social_description string nullable
• promo_headline string nullable
• link_url string nullable
• link_title string nullable
• link_source string nullable
• feed_url string nullable
• stream_articles array (default: [])
  • @type string (default: "ThevergeArticleRef")
  • id integer nullable
  • node_id string required
  • content_type string nullable
  • article_title string required
  • web_url string nullable
  • published_at integer 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 — Story not found (well-formed but nonexistent id or URL, or a URL that is not a story) 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.