Web Archive API
The Web Archive API provides access to historical versions of websites through integration with the Internet Archive’s Wayback Machine. Retrieve archived content, search historical snapshots, and analyze website evolution over time.Credits Required: Archive operations consume 1-2 credits per request (availability checks are free)
Authentication
All archive endpoints require authentication using either:- API Key: Include in
Authorization: Bearer YOUR_API_KEYheader - Session Token: Use Supabase session for dashboard access
Endpoints Overview
Search Snapshots
Find historical snapshots of a URL within date ranges
Retrieve Snapshot
Download content from a specific archived version
Check Availability
Verify if archived versions exist (FREE)
Generate Timeline
Analyze archive history with timeline visualization
Search Snapshots
Search for historical snapshots of a URL, with optional date filtering and result limiting.Request Body
The URL to search for archived snapshots
Specific timestamp in YYYYMMDD format (searches around this date)
Search within a date range
Maximum number of snapshots to return (1-1000)
Archive provider to search. Options:
wayback, archive_today, mementoInclude additional metadata about each snapshot
Return closest available snapshots if exact matches not found
Response
Retrieve Snapshot
Download the actual content from a specific archived snapshot.Request Body
The original URL of the archived page
Exact timestamp in YYYYMMDDHHMMSS format
Archive provider. Options:
wayback, archive_today, mementoResponse
Check Availability
Check if archived versions exist for a URL without consuming credits.Request Body
The URL to check for archived versions
Check availability around specific date (YYYYMMDD format)
Response
Generate Timeline
Generate a timeline showing the archive history of a URL with customizable granularity.Request Body
The URL to generate timeline for
Date range for timeline analysis
Timeline granularity. Options:
day, week, month, yearResponse
Error Handling
The Web Archive API returns standard HTTP status codes and structured error responses:Common Error Codes
400 - Bad Request
400 - Bad Request
Invalid request parameters or malformed data
401 - Unauthorized
401 - Unauthorized
402 - Payment Required
402 - Payment Required
Insufficient credits for the requested operation
404 - Not Found
404 - Not Found
URL not found in archive or no snapshots available
429 - Rate Limited
429 - Rate Limited
Too many requests - please slow down
500 - Server Error
500 - Server Error
Internal server error or Wayback Machine unavailable
Use Cases
Website Evolution Analysis
Track how a website has changed over time by analyzing archived snapshots
Content Recovery
Recover deleted content or previous versions of web pages
Competitor Research
Study competitor websites’ historical changes and strategies
SEO Analysis
Analyze historical SEO changes and their impact
Rate Limits
- Search operations: 60 requests per minute
- Snapshot retrieval: 30 requests per minute
- Availability checks: 120 requests per minute (free operations)
- Timeline generation: 20 requests per minute