Google Maps API arrived much later, but its core ideas—request/response patterns, parameterized URLs, and scripted UI behavior—were forged in 1995–1998 through CGI, HTML forms, and early JavaScript.
Before XMLHttpRequest and the term AJAX existed, developers in 1995–1998 used browser scripting, CGI, forms, and clever page-integration tricks to simulate “dynamic” web apps. This chapter shows the web APIs and constraints that made XHR feel inevitable.
UDDI arrived later, but the urge to catalog and discover services began in the 1995–1998 era of CGI scripts, HTML forms, and early browser scripting. This chapter traces how early dynamic web integration shaped the first “registry-like” patterns in web API history.
From CGI endpoints to form posts and early JavaScript-driven pages, 1995–1998 web integration created “APIs” without contracts—pushing enterprises toward the later idea of discoverable, describable services like WSDL.
In 1995–1998, browser scripting, HTML forms, and CGI quietly acted like early web APIs—revealing integration pain points that later drove SOAP and formal web service contracts. Chapter 77 of our chronological web API history.
From CGI scripts and HTML forms to early browser scripting, 1995–1998 created the need for structured, portable data—setting the stage for XML in web API history.
Between 1995 and 1998, web APIs moved from one-shot CGI responses to stateful experiences. This chapter traces how forms, URL parameters, early JavaScript, cookies, and server-side sessions taught the web to remember users.
Between 1995 and 1998, browser scripting evolved from simple form validation into a recognizable (if messy) web API surface: window/document objects, event handlers, cookies, and the early DOM—bridging static pages with CGI-powered back ends.
From CGI scripts to browser scripting, HTML forms in the mid-to-late 1990s quietly established a repeatable client-to-server contract—an early pattern that looks surprisingly like today’s web APIs.
From 1995 to 1998, CGI scripts and HTML forms acted like early web APIs—defining a practical contract between browsers and servers through query strings, POST bodies, headers, and plain-text responses.