/theverge/authors/articles

POST /api/theverge/authors/articles

Price: 20 credits

List everything one The Verge writer has published, newest first, straight from their author archive. Each story carries headline, excerpt, publish and update timestamps, the byline, the topic taxonomy, the lede image and the live comment count.

How to use it

List the stories written by one The Verge writer, newest first. author takes the slug from https://www.theverge.com/authors/{slug} or the full profile URL; count is how many stories to return and the endpoint walks the archive 10 at a time, so a large count costs proportionally more requests. Each item has id, node_id, article_title, alias, excerpt, web_url, published_at, updated_at, word_count, comment_count, authors[], primary_category, categories[] and image — pass id to theverge/articles for the body. The writer's own profile, bio and socials are in theverge/authors.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• author string required — The Verge author slug or author profile URL (examples: "jay-peters", "https://www.theverge.com/authors/robert-hart"; minLength: 1)
• count integer required — Max number of stories to return (min: 1)

Response

• @type string (default: "ThevergeArticleCard")
• 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)

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 — Author not found (well-formed but nonexistent slug or URL) 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.