Skip to content

Wayback API API

by archive.org

No authHTTPSOpen Data
Open documentation ↗

Overview

API for Internet Archive's Wayback Machine

Wayback API is an open data API from archive.org. It needs no API key. It is served over HTTPS. Its OpenAPI description documents 2 endpoints.

At a glance

Authentication
No auth
HTTPS
Yes
CORS
Unknown
Category
Open Data
Base URL
https://api.archive.org
Version
1.0.0
Endpoints
2
Spec updated
2021-06-21

Make a first request

Replace the placeholders; the documentation says exactly where credentials go.

cURL
curl -X GET "https://api.archive.org/wayback/v1/available" \
  -H "Accept: application/json"
JavaScript
const response = await fetch("https://api.archive.org/wayback/v1/available", {
  method: "GET",
  headers: {
    "Accept": "application/json",
  },
});
const data = await response.json();
console.log(data);
Python
import requests

response = requests.request(
    "GET",
    "https://api.archive.org/wayback/v1/available",
    headers={
    "Accept": "application/json",
    },
    timeout=30,
)
print(response.json())

Endpoints

MethodPathWhat it does
GET/wayback/v1/available—
POST/wayback/v1/available—

Questions

Does the Wayback API API need an API key?

No. The Wayback API API can be called without an API key or sign-up, which makes it handy for prototypes and front-end demos.

Does the Wayback API API support HTTPS?

Yes, the Wayback API API is served over HTTPS.

How many endpoints does the Wayback API API have?

Its OpenAPI description lists 2 endpoints in version 1.0.0. All of them are shown on this page.

What are alternatives to the Wayback API API?

Other Open Data APIs include Search Services, Wikipedia, Nasdaq Data Link, University of Oslo, Data API.

Compare alternatives →

Listed from APIs.guru (CC0).