API integration explained for non-developers, with examples
An API integration is software that moves data between two systems automatically, using the requests each system publishes. How it works, with examples.
By Sohail Hussain16 November 20265 min read
An API integration is a small piece of software that moves data between two of your systems automatically, so nobody has to copy it by hand. An API (application programming interface) is the published list of requests a system accepts, such as "create a contact", "list today's orders" or "mark this invoice as paid". An integration uses the APIs of two systems to pass information from one to the other when something happens: a website enquiry becomes a lead in your CRM, a paid order becomes an invoice in your accounting software, a dispatched order triggers a WhatsApp message to the customer.
Connecting business systems this way is what our APIs and integrations service does. This guide explains the moving parts, so you can judge a proposal or a quote without needing to write code.
What is an API, in plain terms?
An API is a contract. The system promises: send a request in this exact format, and you will get this kind of answer back.
Each request goes to a specific web address, called an endpoint, over HTTPS. It says what it wants, proves who is asking with a key or token, and gets a reply. The reply is usually JSON: structured text where every value is labelled, such as "customer_name", "total" and "due_date". Ask an accounting system for an invoice and you get the customer, line items, tax and total as labelled fields. If you want to see what one looks like, paste a sample into our JSON formatter and it becomes readable.
APIs have versions. Vendors add new ones and retire old ones on a published schedule, which is one reason integrations need looking after.
What does an integration actually do?
Every integration repeats the same five steps: notice that something happened, fetch the details, translate them into the other system's format, send them, and record whether it worked. Some common examples:
| When this happens | Data comes from | And goes to | What moves |
|---|---|---|---|
| A website enquiry is submitted | Website form | CRM | Contact, message, source page, campaign |
| An online order is paid | Store or payment gateway | Accounting | Invoice, payment, tax lines |
| An order is dispatched | Order system | A template message with the tracking link | |
| A deal is won | CRM | Project or job tool | New project with the client's details |
| Stock changes | Accounting or ERP | Online store | Available quantity per product |
Each of these has its own guide: website forms to CRM, the WhatsApp Business API and Tally and Zoho Books integrations.
How does one system know something happened in another?
There are three ways, and the choice decides how fast data moves and how much it costs to run.
| Method | How it works | Typical delay | Good for |
|---|---|---|---|
| Polling | The integration asks every few minutes, "anything new?" | Minutes | Systems that cannot send notifications |
| Webhook | The source system calls your integration the moment something happens | Seconds | Payments, messages, form submissions |
| File exchange | One system exports a file on a schedule; the other imports it | Hours | Older software with no API |
Webhooks are the modern default, and webhooks explained covers how they work and how to receive them safely. Polling still has its place, but every check uses up part of the API's request allowance.
What makes an integration harder than it looks?
Field mapping. Systems disagree about what a customer is. One has a single name field, another wants first and last names. One stores phone numbers with the country code, another without. One uses state names, another needs GST state codes. Most of the work in an integration is agreeing these translations, field by field.
Limits. APIs cap how many requests you can make. As of October 2026, the Zoho Books API allows 100 requests per minute per organisation and between 1,000 and 10,000 a day depending on the plan, according to its API documentation. A sync that ignores limits stops halfway through month-end, which is exactly when volume peaks.
Access. Tokens expire and have to be refreshed. If the connection was authorised with an employee's personal account and that person leaves, the integration can stop the day their account is closed.
Duplicates and order. The same event can arrive twice, or two events can arrive in the wrong order. A well-built integration recognises a repeat and does not create a second invoice.
Failures. The other system goes down for maintenance, or rejects a record because a field is missing. A good integration retries and tells a person. A bad one drops the record silently, and you find out from a customer. Why integrations break covers the habits that prevent this.
Should you use a connector tool or custom code?
Check first whether the two systems already connect natively. Many vendors offer ready-made integrations with popular tools, and a native one is usually the cheapest to run.
If not, connector tools such as Zapier, Make and n8n are good for simple, low-volume flows and can be set up in an afternoon. Custom code is better when volume is high, the mapping is complicated, one system has no connector, or failures must be caught and handled properly. Zapier vs Make vs n8n vs custom code compares them with prices. And when you find yourself connecting four tools with a spreadsheet in the middle, the question becomes whether you need a different tool altogether, which custom software vs off-the-shelf helps you decide.
What should you ask before commissioning one?
- Which system is the source of truth for each piece of data? Customers might belong to the CRM and invoices to accounting.
- Which direction does data move? One-way is simple. Two-way sync of the same record is several times harder, because both sides can change it.
- How fast does it need to be? Seconds, minutes or overnight each lead to a different design.
- What happens when it fails, and who is told?
- Whose accounts hold the keys and the connector subscription? They should be company accounts, not a developer's.
- What does it cost to run each month, including connector fees, hosting and any per-message or per-request charges?
- Who maintains it when a vendor changes its API?
Write the answers to those seven questions on one page before asking anyone for a quote. It turns a vague "connect our CRM to accounting" into something a developer can price accurately, and it often reveals that half the problem is a decision about data rather than code.
Was this guide useful?