GitHub’s API-driven automations didn’t appear out of nowhere. In 1995–1998, browser scripting, CGI endpoints, and HTML forms quietly established the practical patterns—requests, payloads, authentication, polling, and event notifications—that modern developer workflows now take for granted.
In the mid-to-late 1990s, “web APIs” often looked like CGI scripts and HTML form endpoints—yet operators still needed quotas and throttles. This chapter examines how rate limiting quietly became a business and security tool as browsers gained scripting and HTTP traffic scaled.
From CGI scripts to browser scripting and form-driven endpoints, 1995–1998 shaped early developer access control patterns that foreshadowed modern API keys—often implemented with shared secrets, IP allowlists, and basic auth.
OAuth 1.0 arrived much later, but the core problems it solved—third-party access without password sharing—were already visible in 1995–1998 web development patterns like CGI, cookies, and early browser scripting.
From HTML forms and CGI to early JavaScript-driven integrations, 1995–1998 laid the groundwork for public web APIs and the mashup mindset—years before AJAX.
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 first years (1990–1994), HTTP’s stateless simplicity left no room for ad tech as we know it. This chapter traces how early HTTP interfaces and the arrival of cookies set up decades of web advertising—and why today’s Privacy Sandbox APIs are a return to constrained, standardized interfaces.
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.
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.