POST /api/wayback/urls/search
Price: 20 credits
List the distinct URLs the Wayback Machine archived under a site or URL prefix
List every distinct URL the Wayback Machine archived under a site, host or URL prefix, with its content type, first and last capture time, number of captures and a link to its latest capture. Use it to map a site's archived pages or find deleted ones.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)url string required — Site or URL prefix whose archived URLs to list (examples: "iana.org/domains/", "example.org", "https://www.w3.org/TR/"; minLength: 1)count integer required — Max number of distinct URLs to return (min: 1; max: 10000)match_type string — `prefix`: URLs starting with `url`; `host`: every URL of its host; `domain`: every URL of the domain and its subdomains (default: "prefix"; one of: "prefix", "host", "domain")mimetype string nullable — Only URLs whose captures have this content type; a regular expression, `!` negates (examples: "text/html", "application/pdf")status_code string nullable — Only URLs whose captures answered with this HTTP status; a regular expression, `!` negates (examples: "200", "!404")@type string (default: "WaybackArchivedUrl")url string requiredurlkey string nullablemimetype string nullablefirst_captured_at integer nullablelast_captured_at integer nullablecapture_count integer nullableunique_capture_count integer nullablearchive_url string 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.