API
Application Programming Interface: a contract defining how two pieces of software talk to each other. The waiter between your frontend and your backend.
What is API?
Application Programming Interface: a contract defining how two pieces of software talk to each other. The waiter between your frontend and your backend.
API is a foundational concept that sits in the Core Fundamentals area of system design. Engineers reach for it whenever they need to reason about real-world trade-offs in that space — not just for textbook correctness, but because real production systems at companies like Netflix, Amazon, and Google make these decisions every day.
If you want to go deeper than this definition — with diagrams, code, and a quiz to lock it in — work through the "API" lesson linked below. It walks through the why, the mechanism, the trade-offs, and how the giants actually use it in production.
Learn API in depth
Full interactive lesson with diagrams, code examples, real-world references, and a quiz.
Open the API lessonRelated lessons
Lessons that touch on API as part of a larger topic.
API Documentation (Swagger/OpenAPI)
How API specification standards like OpenAPI let teams build, test, and consume APIs without guessing
foundation · core fundamentals
API Keys
The simplest way to identify and authenticate API consumers, a shared secret with limits
intermediate · api design protocols
API Versioning
Evolve your API without breaking existing consumers, strategies for managing change
intermediate · api design protocols
API Rate Limiting
Putting it all together, designing rate limiting for production APIs at scale
intermediate · api design protocols
API Composition
Aggregate data from multiple microservices into a single response at the API layer
intermediate · api design protocols
See also
Related glossary terms you might want to look up next.
REST API
An architectural style for building APIs using standard HTTP methods (GET, POST, PUT, DELETE). Resources are identified by URLs.
GraphQL
A query language for APIs where the client specifies exactly what data it needs. No over-fetching, no under-fetching. One endpoint to rule them all.
gRPC
A high-performance RPC framework by Google using Protocol Buffers and HTTP/2. Much faster than REST for service-to-service communication.