From CERN’s early Web servers to proxies, protocol gateways, and CGI entry points, the years 1990–1994 introduced the core idea behind API gateways: one place to route, observe, and control traffic headed to many backends.
Swagger and OpenAPI feel modern, but their core ideas—contracts, endpoints, headers, and examples—trace back to the Web’s earliest HTTP interfaces. This chapter looks at 1990–1994 documentation practices that quietly set the pattern for today’s API tooling.
A chronological look at 1990–1994, when the Web’s earliest HTTP interfaces and URL conventions laid the groundwork for modern web APIs—providing historical context for developer-first platforms like Stripe.
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 the Web’s earliest years (1990–1994), “APIs” weren’t yet a mainstream product—but HTTP endpoints already needed protection. This chapter traces how rate limiting quietly became a security and business tool as early servers faced scarce resources, buggy clients, and the first automated traffic.
In the early 1990s, the Web had HTTP requests and shared documents—but not “web APIs” or delegated authorization. This chapter traces the authorization reality of 1990–1994 and explains how those constraints foreshadowed OAuth 2.0.
Before JSON, before REST, and before public developer portals, HTML forms quietly created the first mainstream user-to-server API pattern on the early Web—turning clicks into structured HTTP requests.