Long before OpenAPI, developers relied on HTML forms, query strings, and CGI scripts as practical “APIs.” From 1995–1998, browser scripting and early dynamic web integration created implicit contracts that later demanded standardized API descriptions.
Slack’s API-era integrations didn’t appear out of nowhere. In 1995–1998, CGI scripts, HTML forms, early JavaScript, and intranet dashboards established the core patterns—requests, responses, automation triggers, and human-in-the-loop workflows—that later became familiar in Slack apps and webhooks.
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.
Twilio arrived much later, but the API patterns it popularized—parameterized requests, server-side endpoints, and callback-driven workflows—were prototyped on the early web via CGI scripts, HTML forms, and browser scripting between 1995 and 1998.
Long before EventSource and Server-Sent Events, developers in 1995–1998 tried to keep web pages “live” using CGI, forms, frames, and early browser scripting—laying conceptual groundwork for streaming web APIs.
WebSockets weren’t a 1990s technology, but the need for real-time interaction was. From CGI and HTML forms to early JavaScript and frames, 1995–1998 introduced the patterns—and the pain—that later shaped the WebSocket API.
In 1995–1998, the web didn’t have Web Workers—but it definitely had the problem they solve. This chapter traces how early JavaScript, CGI, and form-driven interactivity revealed the need for background processing in browsers.
A focused look at 1995–1998: CGI and forms as de facto APIs, early JavaScript as a client-side interface layer, and why these patterns mattered long before the Canvas API existed.
Long before the Geolocation API standardized location access, mid-1990s developers used forms, CGI, cookies, and early JavaScript to approximate “where” a user was—and tailor content accordingly. This chapter traces how 1995–1998 web building blocks shaped the idea of contextual experiences.
RSS (late 1990s) and Atom (later) are often remembered as “blogging features,” but their real legacy is API-shaped: a stable URL that returns structured, machine-readable updates. This chapter traces how 1995–1998 browser scripting, CGI, and form-driven web apps created the practical and cultural prerequisites for syndication APIs.