The Wayback Machine's CDX API lists every capture of a URL, or of a whole domain, with its date, HTTP status and a content hash. Add collapse=digest and it drops each capture whose content matches the one before it, which leaves the changes.
It is free and needs no key.
Not affiliated with the Internet Archive.
1. On the Wayback Machine website
- Calendar:
https://web.archive.org/web/*/example.comshows the captures of one address by date. Blue dots loaded normally, green are redirects, orange and red are errors. - Every archived address of a site:
https://web.archive.org/*/example.com/*. - Wayback Changes:
https://web.archive.org/web/changes/example.comlets you pick two captures and shows them side by side with the changes highlighted.
Where it stops: these are pages to look at, not a list you can sort in a spreadsheet.
2. The CDX API
Open this in a browser:
https://web.archive.org/cdx/search/cdx?url=example.com&matchType=exact&from=2015&to=2020&filter=statuscode:200&collapse=digest&output=json&limit=3
On 21 November 2026 it answered with a header row and three captures:
[["urlkey","timestamp","original","mimetype","statuscode","digest","length"],
["com,example)/","20150101013824","http://www.example.com/","text/html","200","B2LTWWPUOYAH7UIPQ7ZUPQ4VMBSVC36A","862"],
["com,example)/","20150717015329","http://www.example.com/","text/html","200","E3NHKR6EVSCB7UN54HORD7BEWFEUW332","385"],
["com,example)/","20150717023156","http://example.com/","text/html","200","B2LTWWPUOYAH7UIPQ7ZUPQ4VMBSVC36A","862"]]
| Parameter | What it does |
|---|---|
url |
The page or site to look up |
matchType |
exact (default), prefix (a folder), host (one host), domain (the host and its subdomains) |
from, to |
Dates of 1 to 14 digits (yyyyMMddhhmmss), both inclusive |
filter |
field:pattern. statuscode:200 keeps status 200. |
collapse |
digest drops unchanged captures. timestamp:8 keeps at most one a day, timestamp:4 one a year |
output |
json. Without it you get plain text, one capture per line |
limit |
The first N rows |
The snapshot's address is https://web.archive.org/web/<timestamp>/<original>. With id_ after the timestamp you get the page as archived, without the toolbar. Two rows with the same digest hold the same content.
Rows one and three share a digest. Collapse only compares a row with the row before it, so content that changes and changes back is listed again.
For a list longer than one answer, add showResumeKey=true, then pass the key you get back as resumeKey in the next request.
3. The Availability API
https://archive.org/wayback/available?url=example.com×tamp=20200101 returns the one snapshot closest to that date, in JSON. It answers "is there a copy", not "list them all".
Where the free route stops for a non-programmer: the answer is raw text with no page text in it. Many URLs or long lists need a script to loop and follow the resume key. The Internet Archive blocks clients that ask too fast with a 429 "too many requests" error.
4. The same list as a spreadsheet, with an Apify actor
Internet Archive & Wayback Machine Scraper is an actor we make (details on this site). It sends these CDX requests, follows the resume key and returns one row per capture.
- Open the actor on Apify and sign in. A free account works.
- Mode (
mode): choose "Wayback Machine snapshots". The default is archive.org search. - URLs or domains (
urls): one or more, such asexample.comor a full page address. - Match type (
matchType):exact,prefix,hostordomain. - Collapse (
collapse): "Content changes only" keeps the changes. "One per day", "One per month" and "One per year" thin a long history. - HTTP status filter (
statusFilter):200for pages that loaded,3..for redirects, empty for all. MIME type filter (mimeFilter): for exampletext/html. - From date (
from) and To date (to): YYYY, YYYY-MM or YYYY-MM-DD. - Max snapshots per URL (
maxSnapshotsPerUrl): 100 by default, up to 100,000. - Start the run, then export the rows as CSV, Excel or JSON.
Leave Download page text (fetchContent) off for a list. Tick it to add each page's title and plain text.
One row holds input_url, original_url, timestamp, captured_at (such as 2015-01-01T01:38:24Z), status_code, mimetype, digest, length, snapshot_url and raw_snapshot_url. Exact repeats in the index are skipped and not charged.
Cost: USD 0.50 per 1,000 rows on Apify's free plan, plus Apify's small start fee for each run. Apify's free plan includes USD 5 of credit a month (apify.com/pricing, read 21 November 2026).
Limits
- It lists what archive.org holds. Pages that were never archived, or that the Archive excludes, return no rows.
- On a whole-site list, the day, month and year settings compare each row with the row before it by date alone, so they can skip a page. Use "Content changes only" there.
- There is no "one row per address" setting and no first-and-last summary.
- Archive.org can be slow or refuse requests. The actor waits a second between index pages and retries.
- Respect copyright, the original site's terms and the Internet Archive's terms in what you do with archived pages.
Questions
How do I find the first capture of a page? Use exact and set Max snapshots per URL to 1. The list starts with the oldest capture.
Why are there 404s and redirects in my list? The Wayback Machine keeps what its crawler received, errors included. Set the status filter to 200.