The word comes up as soon as automation is mentioned, and it puts off many people without technical training. That is a shame, because the concept is simple and it determines everything you will or will not be able to automate.
The good news: you do not need to know how to build one. You need to know what it is, and above all to know the one question worth asking before choosing a tool.
Definition
An API, or application programming interface, is the set of entry points through which a piece of software agrees to talk to another piece of software.
Software has two faces. The visible interface, made of buttons and forms, addresses a person. The API addresses a program: same actions, triggered by code rather than by a click.
The service counter is the most accurate image. The API defines what you may ask for, in what format, and what comes back. You do not see what happens behind it, and you do not need to: that is precisely the point.
Why it concerns you
Everything you want to automate assumes your tools can talk to each other. Creating a client record in your CRM when a payment arrives, sending a message when a form is filled in, updating a table when an order changes status: each of these goes through an API.
Hence the question to ask before choosing software, well before comparing features: does it offer an API, and from which plan? Many vendors restrict access to higher tiers. A tool without an API is a tool whose data will stay locked in, forcing you to retype by hand what could travel on its own.
| Without an API | With an API |
|---|---|
| Manual export, retyping, copy and paste | Data travels on its own |
| A human oversight at every step | The same processing every time |
| Volume costs time | Volume changes nothing |
The notions you will meet
The API key
A long code identifying the caller. It is worth a password: whoever holds it acts in your name. It never goes in a shared document, never in an email, never on a page a visitor can view.
The quota
Most APIs limit the number of calls per minute or per day. It is the most frequent cause of an automation that works in a demo and breaks in production, when volume grows.
The webhook
The reverse mechanism. Instead of you asking "is there anything new?", the tool notifies you the moment the event happens. It is cheaper and more immediate, and it is the mechanism most real-time automations rely on.
The documentation
Every API has its own. It states what can be asked. A vendor whose documentation is missing or out of date is a warning sign about the rest of the product.
Best practices
Treat every key like a password. Store it in a dedicated manager, rotate it if in doubt, and above all never leave it in a stray file.
Grant minimum rights. Where the tool allows it, a read-only key for read-only use. Most incidents come from over-permissive keys.
Plan for failure. APIs go down, slow down, change. A serious automation plans for that: a retry, an alert, a queue.
Check the quota before building on it. Do the calculation on your real peak volume, not the average. It is the peak that breaks things.
Frequently asked questions
Do you need to code to use an API?
No. Visual automation tools such as n8n, Make or Zapier call APIs on your behalf: you pick the action from a list and fill in fields. The vocabulary remains useful for understanding error messages, but writing code is no longer necessary.
Do APIs cost money?
It depends on the vendor. Some are included, some restricted to higher plans, some billed per call. For AI models, billing is by Token rather than per call, which completely changes how you estimate a budget.
What happens if the vendor changes their API?
Your automations can stop working. Serious vendors version their APIs and give notice. It is a criterion worth checking when choosing a tool you are going to depend on.
How do you actually connect two tools together?
The simplest route is to start with a single-step case in a visual tool, before chaining complex processing. Our n8n course starts from that first connection and goes through to scenarios that handle errors and volume.