Between 1990 and 1994, the Web’s earliest HTTP interfaces, URL query patterns, and CGI “gateway” scripts quietly established the request/response shape that modern embeddings APIs use for semantic search today.
In the Web’s first years, “APIs” were often just URLs and forms hitting CGI scripts. Those primitive HTTP interfaces introduced a surprisingly modern idea: clients can influence what data they get back—an early ancestor of today’s client-driven data fetching and GraphQL-style thinking.
OpenAPI didn’t exist in the early 1990s, but the Web’s first standards—URLs, HTTP, MIME types, and simple server-side interfaces—introduced the core idea that an API can be described consistently. This chapter traces the roots of standardized API descriptions from 1990 to 1994.
Flickr’s API arrived much later, but the rules it relies on—URLs, HTTP semantics, content types, and server-side gateways—were forged in the Web’s first years. This chapter traces the 1990–1994 interface patterns that made media-sharing integrations possible.
Between 1990 and 1994, the Web’s earliest HTTP interactions weren’t called “APIs,” yet they introduced resource identity, uniform operations, and stateless requests—the same building blocks REST would later formalize.
XML wasn’t yet a web standard in 1990–1994, but the early Web’s HTTP interfaces, CGI scripts, and MIME content types created the exact need XML later filled: predictable, self-describing data that could move cleanly between systems.
In the Web’s earliest years, HTTP’s stateless design collided with real application needs: logins, carts, personalization, and workflow. This chapter traces how developers improvised sessions and how cookies began to emerge around 1994.
Before REST and JSON, CGI scripts turned early websites into programmable interfaces. From 1990–1994, CGI and server-side integration quietly shaped the first usable patterns of web APIs.
Between 1990 and 1994, CGI scripts turned the early Web from static documents into interactive services. This chapter explains how the first practical HTTP interfaces worked—requests as inputs, script output as responses—and how that pattern became the backbone of modern web APIs.