What is an API? (Application Programming Interface)

An API is a defined set of rules that lets one piece of software request something from another without knowing how it works inside.

How does an API work?

One system publishes endpoints. Another sends a request and gets a structured response back, usually JSON over HTTPS, with a key or token identifying the caller. The contract is the whole point: as long as the request and response formats hold, either side can rewrite its internals without breaking the other. REST is the common style, with GraphQL, gRPC, and webhooks covering the rest.

Why do APIs matter?

They are how modern software gets built without building everything. Payments, auth, email, maps, and AI models all arrive as a call instead of a project. They are also a business model on their own. Stripe and Twilio sell nothing but access to their endpoints, and every AI wrapper is a product built on somebody else endpoint.

Where did APIs come from?

The concept dates to the 1940s and 1950s as a way to describe interfaces between program components. Web APIs arrived around 2000 with Salesforce and eBay, then became a discipline at Amazon in 2002, when Jeff Bezos reportedly ordered every internal team to expose its data through service interfaces or be fired.

How do you use APIs well?

Read the rate limits and the pricing before you design around them, because both will shape your architecture. Handle failure on purpose: retries with backoff, timeouts, and a plan for when the vendor is down. Never put keys in client code. And ask what happens if this vendor triples the price or turns the endpoint off, because depending on someone API means depending on their roadmap.

Bottom line: An API is a promise about how to ask, and that promise is what lets software stack.

For more startup terminology, visit startupdefinitions.com.