/theverge/articles/search

POST /api/theverge/articles/search

Price: 10 credits

Full-text search across the whole The Verge archive back to 2011. Each hit carries the headline, the excerpt, a keyword-in-context snippet, publish and update timestamps, the credited authors, the section and topic it was filed under, the full parsely tag list and the lede image. The source serves at most 100 hits per query however many stories actually match.

How to use it

Search The Verge by keyword. keyword is required and count is capped at 100, which is the source's own ceiling even when tens of thousands of stories match. Results are relevance-ranked, not chronological, and there are no section or date filters: to browse a topic in date order use theverge/categories/articles, and to browse one writer use theverge/authors/articles. Each item has id, web_url, article_title, excerpt, snippet, published_at, updated_at, author_names[], section, topic, tags[], content_type and image. Pass web_url to theverge/articles for the full body: id is the same numbering theverge/articles and the listing endpoints publish, and it is null for the pre-2025 stories whose URL carries a legacy Chorus number instead, so join on web_url when it is null. is_resolvable is false for the few indexed pages theverge/articles cannot serve — the site root and the legacy /a/ long-form features, which the site publishes outside its CMS.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string required — Full-text query matched against the whole verge archive (examples: "openai"; minLength: 1)
• count integer required — Max number of stories to return, capped at 100 by the source (min: 1; max: 100)

Response

• @type string (default: "ThevergeSearchResult")
• id integer nullable
• node_id string nullable
• article_title string required
• web_url string required
• is_resolvable boolean (default: false)
• excerpt string nullable
• snippet string nullable
• published_at integer nullable
• updated_at integer nullable
• author_names array (default: [])
• section string nullable
• topic string nullable
• tags array (default: [])
• content_type string nullable
• image string nullable
• image_alt string nullable
• thumbnail 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 — The entity was not found, or a precondition failed 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.