/theverge/authors

POST /api/theverge/authors

Price: 10 credits

Get a The Verge writer by slug or profile URL: display name, staff job title, the short byline bio and the long profile biography, portrait, personal RSS feed, and every social account the newsroom publishes for them — Bluesky, Mastodon, Threads, TikTok, X, LinkedIn, Instagram, Facebook, personal site and work email.

How to use it

Fetch a single The Verge writer. Accepts the slug from https://www.theverge.com/authors/{slug} (hyphenated, for example 'jay-peters') or the full profile URL. Returns one item with name, job_title, short_bio (the one-line byline blurb), description (the full profile bio), image, feed_url (their personal RSS feed), email and the bluesky/mastodon/threads/tiktok/twitter/linkedin/instagram/facebook/homepage URLs, plus archive_pages, the number of 10-story pages their archive holds. Use theverge/authors/articles to read what they wrote.

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: "robert-hart", "https://www.theverge.com/authors/jay-peters"; minLength: 1)

Response

• @type string (default: "ThevergeAuthor")
• id integer nullable
• node_id string required
• name string required
• alias string required
• web_url string nullable
• job_title string nullable
• short_bio string nullable
• description string nullable
• image string nullable
• feed_url string nullable
• archive_pages integer nullable
• email string nullable
• bluesky_url string nullable
• facebook_url string nullable
• instagram_url string nullable
• linkedin_url string nullable
• mastodon_url string nullable
• threads_url string nullable
• tiktok_url string nullable
• twitter_url string nullable
• homepage_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 — 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.