Archive.org API

Beginner's Pick Open Data / No Auth Required Beginner HTTPS
Free to Use
59 C
Measured Score 0 50 100 Speed 16/30 Consistency 4/20 Security 20/20 Browser access 15/15 Transparency 4/15 TESTED 2026-08-10

Overview

The Internet Archive API gives you programmatic access to the Wayback Machine and one of the world's largest digital libraries, containing archived websites, books, audio, video, and software. No API key is required to start exploring the archive. It is a powerful tool for researchers, archivists, and developers working with historical web content.

Beginner Tip

Use the Wayback Availability API to check whether a URL was ever archived — just pass the URL as a query parameter with no authentication required. For searching the full collection, use the archive.org/advancedsearch.php endpoint with output=json.

Measurement Record

What actually happened when we called this API from our own infrastructure. Every value below was recorded by the request, not copied from the provider's documentation.

Request
GET https://archive.org/wayback/available?url=example.com
Result
HTTP 200 · application/json · 200 bytes
Response time
241 ms (median of 3) · fastest 146 ms
Transport
TLSv1.3 · TLS_AES_256_GCM_SHA384 · certificate issued by GoDaddy.com, Inc.
Browser CORS
Allowed — Access-Control-Allow-Origin: *
Served by
nginx/1.31.3
Recorded
2026-08-10

Fields Returned

Top-level fields present in the response we captured, with the type and value we actually received.

Field Type Value received
url string example.com
archived_snapshots object {1 fields}

Captured Response

Captured from a real request to https://archive.org/wayback/available?url=example.com on 2026-08-10. Long arrays and nested objects are truncated to keep the shape readable.

JSON Response · Captured
{
  "url": "example.com",
  "archived_snapshots": {
    "closest": {
      "status": "200",
      "available": true,
      "url": "http://web.archive.org/web/20260810033727/https://example.com/?",
      "timestamp": "20260810033727"
    }
  }
}

Field Reference

url The original URL you submitted in the request

Implementation Example

Calls a real endpoint of this API. Replace any placeholder credentials with your own key.

Request
const url = "https://archive.readme.io/docs";
const response = await fetch(url);
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
const data = await response.json();
console.log(data);

What Can You Build?

Note: These code examples are AI-generated and unverified. Always refer to the official API documentation for accurate usage.

How This API Fails

We deliberately sent this API a broken request and recorded exactly what came back on 2026-08-10. Knowing the shape of an error before you hit it makes error handling much easier to write.

HTTP 429 Requesting a path that does not exist text/html

Returned an HTML error page rather than JSON — worth knowing if your client assumes every response can be parsed as JSON.

HTTP 429 Sending an invalid value for "url" text/html

Returned an HTML error page rather than JSON — worth knowing if your client assumes every response can be parsed as JSON.

Common Errors & Troubleshooting

Generated guidance based on this API's documentation, not observed by us. Treat it as a starting point and check against the provider's own error reference.

Snapshot not available The URL you requested has not been archived by the Wayback Machine
Try a different timestamp or check that the URL is correct; use the availability endpoint to confirm before fetching
429 Too Many Requests You are making requests too quickly against the public API
Add a delay between requests (at least 1 second) and avoid parallel requests to stay within acceptable usage guidelines
Empty results from search The search query returned no matching items in the archive
Simplify your query parameters, check for typos in field names, and refer to the advanced search documentation for correct syntax

Measured Score Breakdown

Live HTTP request to the API endpoint

Speed 16/30
Consistency 4/20
Security 20/20
Browser access 15/15
Transparency 4/15
Endpoint Response Time 241ms

Fully tested on Aug 10, 2026

Technical Specifications

Auth No Auth
HTTPS REQUIRED
CORS NO
Category Open Data
Difficulty Beginner
Endpoint last called: 2026-08-10

Related Tags

Similar APIs

View All →