From HTTP’s earliest request/response patterns to the first practical server interfaces, 1990–1994 quietly planted the design instincts behind today’s composable web APIs—uniform URLs, simple verbs, and the idea that you can stitch capabilities together through links and messages.
From HTTP’s earliest request/response patterns to CGI scripts and directory-like endpoints, 1990–1994 set the API-shaped foundation that FHIR later embraced for healthcare interoperability.
From the birth of the Web to Mosaic-era growth, 1990–1994 quietly introduced the first monetized, API-like products: HTTP gateways, CGI scripts, and paid data access—long before “API marketplaces” became a category.
In 1990–1994, the Web’s “API surface” was mostly URLs, HTTP methods, and early server scripts—not JavaScript calling APIs. This chapter explains how that era set up the later need for CORS and modern cross-origin rules.
In the Web’s first years (1990–1994), HTTP was tiny, servers were simple, and “APIs” mostly meant speaking basic request/response over the network. Those constraints later produced AJAX—and eventually the Fetch API, which modernized the same fundamental idea.
WebRTC arrived decades later, but its DNA traces back to the Web’s first years: early HTTP rules, headers, content types, and gateway patterns that taught browsers how to negotiate capabilities.
Long before Twilio made communications programmable, the early Web (1990–1994) established the practical building blocks of web APIs: URL addressing, request/response patterns, and simple server interfaces that taught developers how to “call” a service over HTTP.
Server-Sent Events (SSE) arrived much later, but the need for streaming updates was visible from the Web’s earliest days. This chapter traces how HTTP’s simple request/response model (1990–1994) created both the problem—and the early experiments—that led to modern streaming web APIs.
In 1990–1994, the Web didn’t have a Canvas API—yet early HTTP interfaces, URLs, MIME types, and server-side image generation established the core API patterns that later enabled rich visual web applications.
Long before browsers exposed precise location, early HTTP servers and CGI scripts (1990–1994) improvised “where are you?” signals using IP addresses, DNS, and user input—foundational ideas that later shaped the Geolocation API and modern contextual web experiences.