APIs are what let two pieces of software talk to each other without a person clicking through a website in between. One program sends a request against a defined set of rules and endpoints, and gets back a structured response - usually in JSON - describing the data or confirming the action.
Example
A weather app has no idea what the temperature is on its own - it asks a weather service’s API for the forecast in a given city, and displays whatever structured data comes back.
n8n relevance
Calling APIs is what most n8n workflows are actually doing under the hood. Hundreds of built-in nodes are really just pre-configured wrappers around a specific service’s API, and when no ready-made node exists, the HTTP Request node lets you call any API directly - setting the URL, method, headers, authentication and body yourself. Reading API docs, understanding authentication, and troubleshooting error responses all come up early in n8n training, since APIs are what connect a workflow to almost any tool, CRM, or AI service out there.
Related concepts
Closely related: Webhook, JSON and Credential.