What Is an API Gateway? A Liberal Arts Student's Perspective
 # What Is an API Gateway? A Liberal Arts Student's Perspective In 1947, the psychologist Kurt Lewin noticed something ordinary: the food that reaches a family's dinner table doesn't get there by accident. Someone — usually a housewife, in Lewin's framing — decides what passes through the kitchen "gate" and what doesn't. Lewin called this act "gatekeeping," and the idea reshaped how we understand power, media, and access. It traveled from dinner tables to newsrooms, where a 1950 study of a newspaper editor nicknamed "Mr. Gates" showed how one person's choices shaped what thousands of readers believed was important. You don't need to write code to understand what an API gateway is. In fact, the conceptual tools you already carry from the humanities — ideas about translation, borders, power, and language — are precisely the right ones. In 2025, Postman's State of the API report found that 82% of organizations had adopted some form of API-first approach, with 25% going fully API-first ([Postman](https://www.postman.com/state-of-api/2025/), 2025). Almost every digital interaction you make now passes through a gatekeeper you've never seen. By the end of this essay, you'll know what an API gateway actually does — and you'll have a sharper lens on gatekeeping itself. > **Key Takeaways** > - An API gateway is the internet's gatekeeper: one entry point that controls, translates, and protects traffic (Lewin 1947). > - In 2025, 98% of organizations faced API security problems (Salt Security, 2024). > - Four jobs — authentication, rate limiting, translation, logging — map onto ideas you know: borders, bouncers, switchboards. > - A gateway is never neutral; it's policy wearing the mask of infrastructure.