POST /api/wayback/pages/search
Price: 20 credits
Full-text search of archived pages inside a Wayback Machine collection
Search the text of archived web pages inside one Wayback Machine collection (GeoCities, .gov sites, news archives, PDFs and more). Returns each page's URL, title, extracted text, matching excerpts and first capture time. Narrow by language, site, or publication year and month.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)query string required — Words to look for in the archived pages' text (minLength: 1)collection string required — The full-text-indexed Wayback Machine collection to search in (one of: "FOIAonline.gov", "epstein-files", "geocities", "HongKong", "cmt.com", "dcist.com", "elperiodico.com.gt", "eric.ed.gov", "files.eric.ed.gov", "january6th.house.gov", "local-news-us", "mtv.com", "pastebin.com", "cia-world-factbook", "covid", "hkcnews.com", "northkorea", "tammybruce.com", "themessenger.com", "time.com", "realdonaldtrump", "congress.gov", "exiledonline.com", "gawker.com", "EndOfTermWebCrawls", "EndOfTerm2008WebCrawls", "EndOfTerm2012WebCrawls", "EndOfTerm2016WebCrawls", "EndOfTerm2020WebCrawls", "EndOfTerm2024WebCrawls", "EndOfTerm2024Videos", "gov", "gov-pdf", "badoo.com", "hk.appledaily.com", "mediacloud", "nrc.gov", "pdf", "presentations", "independent-media-afghanistan", "independent-media-belarus", "independent-media-central-america", "russian-independent-media", "thestandnews.com", "unicef", "us-state-department", "poetry.com", "scmp.com", "telegram", "towcenter-pink-slime-news-sites", "vice.com", "zaman.com.tr"; examples: "geocities")count integer required — Max number of pages to return (min: 1; max: 1000)sort string — Result order: best match first, most recently captured first, or earliest first (default: "relevance"; one of: "relevance", "newest", "oldest")language string nullable — Two-letter language code of the page text (examples: "es"; minLength: 2; maxLength: 3)site string nullable — Only pages from this domain or top-level domain (examples: "org", "physforum.com")published_year integer nullable — Only pages published in this year (examples: 2007; min: 1990; max: 2100)published_month integer nullable — Only pages published in this month of `published_year` (examples: 9; min: 1; max: 12)@type string (default: "WaybackPage")url string requiredurlkey string nullablehost string nullabledomain string nullabletld string nullabletitle string nullabletext string nullablehighlights array (default: [])content_type string nullablefirst_captured_at integer nullableduplicates array (default: [])@type string (default: "WaybackPageDuplicate")url string requiredurlkey string nullablehost string nullabledomain string nullabletld string nullabletitle string nullabletext string nullablehighlights array (default: [])content_type string nullablefirst_captured_at integer nullable422 — 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.