API (Application Programming Interface)
A structured way for software systems to talk to each other, like a menu that lists what you can ask a service to do and how to ask for it.
What It Is
An API is a set of rules that lets one piece of software communicate with another. When you use a weather app on your phone, it does not generate the forecast itself. It sends a request to a weather service’s API, which returns the data in a structured format the app can display. APIs work like a restaurant menu: you see what is available, you place your order in the expected format, and you get back what you asked for. You do not need to know how the kitchen works. Most modern software is built by connecting APIs together rather than building everything from scratch.
Why It Matters
Nearly every AI tool, automation platform, and web service you will use as an operator communicates through APIs. When you connect Claude to your workflow in n8n, you are using Anthropic’s API. When you send emails through Resend, you are using their API. When you store data in Supabase, you are using its API. Understanding the concept of APIs, even without writing code, helps you understand how tools connect, what is possible, and why some integrations work smoothly while others require more setup.
In Practice
When you see “API key” in a tool’s settings, that is your credential for accessing their API. When a tutorial says “call the endpoint,” it means send a request to a specific URL that the API provides. Most operator-level work involves configuring API connections in visual tools like n8n rather than writing raw API calls, but knowing what is happening under the hood helps you troubleshoot when things break.