Between 1990 and 1994, the Web’s earliest HTTP interfaces pushed a surprising innovation: documentation that behaved like a product. In Chapter 69, see how URLs, hypertext manuals, and early developer expectations set patterns that web APIs still follow.
In the Web’s earliest years, browsers didn’t ask for camera, location, or notification access—because they couldn’t. This chapter traces how early HTTP and HTML interfaces quietly defined privacy expectations long before formal browser permissions APIs existed.
Long before “Jamstack” had a name, early Web builders were already practicing its core idea: prebuilding pages from remote data. In 1990–1994, HTTP’s simple request/response model, early gateways, and CGI scripts laid the groundwork for build-time API consumption—even if nobody called it that yet.
In the Web’s earliest years, developers used simple HTTP interfaces, CGI scripts, and server modules to stitch together internal systems. This chapter traces how those early patterns anticipated microservices and modern internal API ecosystems.
Before “web APIs” had a name, early HTTP and the newborn World Wide Web (1990–1994) established the core patterns APIs still use: resources, stateless requests, URIs, and a simple request/response contract.
Chapter 1 (1990–1994) of web API history: how early HTTP turned the newborn Web into a programmable interface—long before “REST” and “JSON” became everyday terms.