API
The “window” where apps talk to each other
API stands for Application Programming Interface. In everyday words: a well-defined set of rules for one program to ask another for work or data without needing to know its entire kitchen.
Waiter and kitchen
Picture a restaurant. You (the client app) do not barge into the kitchen (the server’s internal system). A waiter takes your order, passes it the right way, and brings the dish—that boundary role is a lot like an API.
- Guest (you): The app or user action that wants something.
- Kitchen (chef): The system that actually has the data or does the work.
- Waiter (API): The agreed, stable list of “how to order” and “what comes back”.
Because the “menu” is public and versioned, many different devices can all order the same way. That’s what lets ecosystems interoperate.
Where you already use APIs
Browsing, you are rarely aware of the calls, but the pattern is constant:
- Sign−in with…: Your app hands off identity work to a provider through their API.
- Embedded maps: A page asks a map service for tiles and routes through defined endpoints.
- Online checkout: The shop talks to a payment network via APIs instead of building banking from scratch.
The site “borrows” a capability—under contract, with keys and permissions—instead of re−inventing every subsystem.
Summary
An API is a shared, stable interface. It is why your phone, the web, and server farms can all cooperate—without each app prying the others’ covers off.
sell Tags
book Related
