API Changelog

GeoCities HTML Parser Memory Leak Resolved

Fixed an issue where malformed table structures in 1996–1998 GeoCities archives caused increased memory consumption during batch retrieval operations.

• GET /archive/batch - Memory usage reduced by 40% for legacy table-based layouts

New Snapshot Rendering Endpoints

Introduced endpoints to request server-side rendered snapshots of archived pages using era-specific browser engines (Netscape 4.0x, IE 5.0).

GET /render/snapshot/geo_1997_home_482 HTTP/1.1
Host: api.1990webarchive.com
X-Engine: netscape-4.04-win
Accept: application/html

• GET /render/snapshot/{id} - New endpoint
• POST /render/batch - New endpoint

X-Auth-Token Header Deprecation

The legacy X-Auth-Token header is deprecated. All clients must migrate to Bearer token authentication. Legacy tokens will stop working on 2025-04-01.

# Before (Deprecated)
curl -H "X-Auth-Token: legacy_key_1990" /api/v3/archive/search

# After (Required)
curl -H "Authorization: Bearer eyJhbGc..." /api/v3/archive/search

Advanced Filter Operators & Rate Limit Headers

Added support for boolean operators in search queries. Standardized rate limit response headers across all endpoints.

• GET /archive/search - Added &op=AND|OR parameter
• All responses now include X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset

Major Version 3.0 Release

Complete API overhaul for improved performance, standardized JSON responses, and unified error codes. v2 endpoints are no longer supported.

- Base path changed from /api/v2 to /api/v3
- Response format changed from snake_case to camelCase
- Pagination replaced with cursor-based model
- Error object now includes 'requestId' field

Rate Limit Enforcement & Abuse Prevention

Implemented stricter rate limiting on archival retrieval endpoints to prevent scraping of unindexed deep-web collections. Updated WAF rules.

• GET /archive/{url} - Reduced to 60 req/min for unauthenticated requests
• New 429 Too Many Requests response format with retry-after header