What is an API? A plain-language guide for business owners

API stands for Application Programming Interface. In plain words, it is a doorway that lets one program ask another program for data or for an action. Think of a restaurant: you (a program) tell the waiter (the API) what you want, the waiter takes the order to the kitchen (another system) and brings back the result. You never need to know how the kitchen works, and the kitchen never needs to know who you are, only that you ordered correctly.

How it works

1. Program A sends a request: "give me the status of order 123".
2. Program B checks that A is allowed to ask (usually with a secret key).
3. Program B sends back a response: "shipped, arrives Tuesday".

A simple request and response can look like this:

GET /orders/123
→ { "id": 123, "status": "shipped", "delivery": "Tuesday" }

That is all an API is: a clear question and a clear answer, in a format that programs understand.

Where you already use APIs

• Your web shop sends a payment to the bank or card provider, and gets back "paid" or "declined".
• A map appears on your contact page, supplied by a map service.
• A new form submission lands in your CRM and in your team chat at the same moment.
• Your accounting program fetches invoices from the web shop automatically.
• A shipping widget shows live delivery prices from the carrier.
• Your email newsletter tool adds new customers to the right list.

Why it matters for your business

• Less manual work: data moves between systems without retyping. If someone in your team copies numbers from one screen to another, an API can probably do it.
• Fewer mistakes: no copy-and-paste errors, no forgotten steps.
• Flexibility: you can connect new tools without rebuilding everything, and replace one tool without breaking the rest.
• Faster launches: you reuse ready services (payments, maps, email, login) instead of building them yourself.

Example. A small training company used to get course bookings by email and then copy them into a spreadsheet and the invoicing program. By connecting the booking form, the spreadsheet and the invoicing tool through their APIs, each booking now creates an invoice automatically, and the receptionist saved about five hours per week.

Common types of API

• REST: the most common. Simple web addresses and standard actions (read, create, change, delete). Easy to start with.
• GraphQL: the program asks for exactly the fields it needs and nothing more. Useful for complex apps.
• Webhooks: the opposite direction. The other system calls you when something happens, for example "payment received".

Advantages and things to watch

• Security: keep API keys secret, use HTTPS and give each program only the access it needs. A leaked key is like a leaked password.
• Limits: many services restrict how many requests you can send per minute or per day.
• Changes: providers update their APIs from time to time, so connections need occasional maintenance.
• Cost: some APIs are free, others charge per request. Check this before you build on them.
• Dependence: if the other service is down, your connection stops too. Plan what happens then.

What to ask your developer or supplier

• Does the tool we want to buy have an API, and is it included in our plan?
• What exactly can we automate with it?
• Who looks after the connection if something changes?
• How are keys stored and who can see them?

A good API often decides whether a program will fit into your business or become one more isolated island that needs manual work.