Category
Knowledge base
Subject
API & integrations
Reading time
Extensive
Level
Decision maker
Updated
May 2026

API integration: what is it and how does it work?

A complete explanation of APIs and API integrations — what they are, how they work technically, which types exist and when to use them. Written for founders, product managers, marketers and sales: anyone who wants to understand the concept without being a developer.

What is an API?

API stands for Application Programming Interface. It is the way software systems talk to each other — a fixed set of rules that lets programs request or send data without a human in between.

The easiest analogy is a restaurant. You sit down, get a menu and give your order to the waiter. The waiter walks to the kitchen, passes it on, and comes back later with your dish. You don't know how the kitchen works and you don't need to — you only know the menu and the rules of ordering. In this story, the waiter is the API: a standardised counter between you and the kitchen.

An API has no visual layer, no buttons and no design. It is purely data going back and forth via requests (requests) and responses (responses). In the vast majority of modern software this happens over the HTTP protocol — the same protocol your browser uses to fetch a web page. Beneath that there are several styles: REST, GraphQL, SOAP and gRPC are the best known.

i
In short

An API is not a button or a screen — it is a set of rules that lets two software systems exchange data in a structured way. No UI, just requests and responses.

What is an API integration?

An API integration is the link between two or more systems via their APIs. It is the concrete piece of software that makes one API talk to another, automatically, at fixed times or as soon as something happens.

The difference from manual work is big. Without an integration, someone exports orders from the webshop to Excel, then opens the accounting package and retypes the data. With an integration, every new order appears in your accounting immediately, without anyone lifting a finger. Same data, different route — and that route scales as your business grows.

A good API integration is more than just "data from A to B". It also handles the exceptions: what do you do if system B is briefly unavailable? What if the same order accidentally comes through twice? What if the structure of a field changes? These constraints determine whether an integration keeps working in production or quietly loses data. We cover them in detail on our page about smart API integrations.

Types of API: REST, GraphQL, SOAP and more

Not every API works the same way. The underlying style determines how a developer works with the API — and in which cases that style makes sense.

REST API

The de facto standard of the modern web. REST works over HTTP, uses JSON for data and is easy for humans to read. Virtually every SaaS tool you know — HubSpot, Stripe, Shopify, Slack — offers a REST API. Request something via a URL and you get a structured response back. Simple in design, and enough for most use cases.

GraphQL

A newer alternative, originally from Facebook. With GraphQL, the query describes exactly which fields you want back — no more, no less. It is handy for complex data models where you would otherwise need many separate REST calls. Shopify, GitHub and many headless CMS platforms offer GraphQL.

SOAP

The predecessor of REST. SOAP uses XML, is much more rigidly defined and is rarely used for new builds in modern contexts. You will come across it in enterprise environments: old banking systems, government services and large ERP packages. A SOAP integration takes more work, but for anyone who has to talk to a legacy system it is often the only option.

gRPC

A binary protocol from Google, designed for performance-critical scenarios between internal services. You rarely encounter it in B2B integrations — more often within the architecture of a SaaS product itself.

WebSocket

Not request-response, but a permanently open connection over which both sides can send data at any moment. Essential for chat applications, dashboards that need to update live, or trading platforms.

Webhooks

Strictly speaking not an API style but a mechanism: instead of you repeatedly asking "is there anything new?", the source system sends a signal as soon as something happens. An order, a payment, a status change — pushed straight to your own endpoint. Webhooks are the standard for event-driven integrations.

The choice between these styles is rarely a matter of principle: you use what the vendor offers. It is worth checking in advance what a SaaS supplier supports before you promise an integration, though. An older package that only offers SOAP calls for a different kind of work than a modern tool with REST and webhooks.

How does an API integration work technically?

Under the hood, every API call goes through the same steps. For decision-makers it is useful to know them in outline — not to build them yourself, but to ask a supplier the right questions.

Authentication

An API needs to know who is knocking. The three most common methods are API keys (a long secret key sent with every request), OAuth 2.0 (a token flow in which a user explicitly grants permission) and JWT (a signed token containing the identity). OAuth is the standard for user-facing integrations; API keys suit server-to-server.

Request

The request consists of an HTTP method (GET to retrieve something, POST to create something, PUT or PATCH to modify something, DELETE to remove something), a URL that identifies the resource, and an optional body containing data.

Response

The response contains a status code (200 = fine, 4xx = your error, 5xx = their error) and a payload with the requested or confirmed data — usually JSON.

Rate limits

Almost every API limits the number of requests per second, minute or day. If you exceed that limit, you temporarily stop getting responses or are even blocked. A good integration takes those ceilings into account and builds in delays where needed.

Error handling and retries

Networks falter. Servers go offline briefly. A production-grade integration retries failed requests with increasing intervals (exponential backoff), and stores what failed so it can still be processed later.

Pagination

With large datasets, an API does not return everything in one go. You request one "page" at a time (for example 100 records per request) until you reach the end. Forgetting to paginate is a classic reason why an integration works fine in testing but misses data at real volumes.

Idempotency

A well-designed API lets you send the same request several times without it being processed twice — for example by supplying a unique key per order. For payments and orders this is essential. Without idempotency, a customer may in the worst case pay twice, or the same invoice ends up in the accounts twice.

Versioning

SaaS suppliers update their APIs regularly. Old versions usually keep working for a while, but they expire at some point. A production integration actively watches the vendor's announcements and plans the upgrade path — otherwise you will one day find your synchronisation has ground to a halt.

!
Tip

Ask a supplier how the integration handles rate limits, retries and pagination. Three questions that immediately show whether someone has built production integrations or only knows a quick prototype.

Examples from practice

A few integrations we come across often in practice, all familiar for SMEs and scale-ups:

  • CRM → accounting: a new customer in HubSpot or Pipedrive automatically appears as a contact in Exact, Twinfield or Moneybird. No double entry, no wrong address fields.
  • Webshop → ERP: a Shopify or WooCommerce order flows straight into your ERP or inventory system (SAP, Magento, Picqer). Stock, order status and invoicing stay in sync.
  • ATS → payroll: when a candidate is hired in Bullhorn or Recruitee, their employee record is created directly in NMBRS or AFAS.
  • WhatsApp → CRM: incoming customer messages appear as a ticket in Zendesk, HubSpot or Freshdesk, including the full conversation history.
  • Calendly → CRM: a scheduled appointment automatically updates a lead stage and sends the right follow-up.
  • Payment provider → accounting: Mollie, Stripe or Adyen payments are matched to invoice statuses, so a received payment immediately closes the outstanding item.

The biggest leap rarely comes from a single integration, but from how they work together: three to six systems feeding each other instead of isolated silos. If you want to see more of how we approach this, take a look at our page on integrations as a service.

A nuance that often gets lost in lists like this: not every integration needs to be real-time. For an accounting integration, a nightly batch is often perfectly fine, and cheaper to build. For a payment confirmation in a webshop, it has to happen within seconds. Make that trade-off per data flow, not as a blanket policy for the whole organisation.

iPaaS versus custom API integration

An API integration doesn't always have to be custom. There are so-called iPaaS platforms (Integration Platform as a Service) that standardise a large part of the work.

iPaaS: Zapier, Make, Workato, n8n

With an iPaaS, you click an integration together in a visual editor: a trigger from system A, an action in system B. For simple scenarios, it's quick, inexpensive and needs no code. It's excellent for automating standard flows between widely used SaaS tools.

Custom integration: your own middleware

Once the logic gets more complex, with a lot of field-by-field mapping, business rules, fraud checks, performance requirements or an in-house ERP, iPaaS hits its limits. At that point you build (or commission) your own middleware layer: a small piece of software that handles the translation between the systems, provides monitoring and takes care of queueing.

It isn't an either/or choice: many organisations combine the two. A Zapier flow for the simple work, custom middleware for business-critical processes. We cover the difference between the two approaches in detail in our guide to APIs versus integration platforms.

Which companies benefit from an API integration?

The tipping points in our experience:

  • SMEs with three or more separate SaaS tools: as soon as people retype data between applications every day, an integration almost always pays for itself.
  • Growing scale-ups: what can be done manually with a hundred transactions breaks down at a thousand a day. Integrations are a growth enabler.
  • Enterprises with a multi-vendor stack: large organisations rarely run on a single package. Integrations keep ERP, CRM, HR, finance and BI aligned.
  • Industry bodies and marketplaces: when you exchange data with partners, suppliers or members, an API integration is the scalable solution for what used to happen in emails and spreadsheets.

We work with SMEs considering their first integration as well as with enterprises looking to consolidate their existing integration landscape. For background on this, see our systems integration specialist page.

What does an API integration cost?

There's no fixed price tag, and anyone who quotes one without first knowing the scope is selling you a fairy tale. What we can say is how the range builds up:

  • iPaaS integration: a simple flow between two well-known SaaS tools sits at the lower end of the budget. No middleware needed, little business logic, mostly configuration work.
  • Custom integration: costs scale with the number of systems, the complexity of the mapping, how many exceptions need handling and industry requirements (finance, healthcare and government impose additional requirements).
  • Maintenance: every integration needs maintenance. API versions change, suppliers modify fields, and your own processes evolve. Budget for an ongoing maintenance cost, expressed as a percentage of the build cost rather than a fixed figure.

The biggest pitfall in budgeting is forgetting monitoring and error handling. Delivering an integration that "works" is cheap; an integration that is still processing data reliably a year from now takes a little more.

Two hidden cost items that people tend to overlook: documentation and knowledge retention. If the developer leaves and nobody knows how the mapping works any more, you end up paying for the integration again at some point in the future. For every integration, ask for a short technical readme covering which endpoints, which fields and which exceptions. That document is worth more than an extra feature.

GDPR and compliance in API integrations

As soon as personal data passes through an API (names, email addresses, phone numbers, customer numbers, payment details), the GDPR applies in full. There are several things you should expect to see in any serious integration:

  • A DPA with every party: a data processing agreement with the vendor or the iPaaS platform that the data passes through.
  • Encryption in transit: all traffic over TLS (HTTPS). No plain HTTP, no unencrypted queues.
  • Audit log: who requested, changed or forwarded what. Essential in the event of incidents or data subject access requests.
  • Data minimisation: only send what you need. Not "the entire customer profile, just to be safe".
  • Retention periods: if the middleware temporarily buffers data, a retention period should apply.

For industries with additional frameworks (healthcare, finance, government), specific requirements come on top of this. A serious integration partner will raise these proactively.

Common mistakes in API integrations

Almost all the problems we come across fall into the same handful of categories:

  • No respect for rate limits: the integration hammers the API with requests until the vendor cuts off access. Everything then grinds to a halt.
  • No error handling: when something fails, nothing is logged and nothing is retried. Data simply disappears into thin air.
  • Hardcoded credentials: API keys in the source code or in a Git repository. One leak and you have a security incident on your hands.
  • No logging or monitoring: you only discover an outage when a customer calls. That is too late.
  • No idempotency keys: when something hiccups, the same order gets processed twice, and you only find out in the accounts.
  • Overly tight coupling: a change in one system immediately breaks five other processes. A good integration isolates that.

None of these pitfalls is exotic, and every one of them is avoidable. The difference lies in the discipline of whoever builds the integration and in a serious approach to testing and monitoring.

One additional point that is often underestimated: testing with production-like data. An integration that works with three test customers can still fall over on real volumes because of edge cases: special characters in names, empty fields, customers created long ago with a different structure. Plan a phase in which the integration runs in parallel alongside your current process before you switch over for good.

Do it yourself or outsource?

Not every integration needs to be outsourced. A few rules of thumb:

Do it yourself

You have a simple flow between two SaaS tools, an in-house developer or a tech-savvy operations colleague, and no critical processes or large volumes are at stake. A Zapier or Make flow is then often enough.

Outsource

It gets more complex once multiple systems come together, custom middleware is needed, GDPR requirements are strict, or the integration becomes part of your core process. At that point it pays to bring in a partner who sees the full picture, from architecture to monitoring to maintenance.

There is a lot of room between those two extremes. A common route is for an external party to build and document the integration, with an in-house colleague managing it afterwards. Which split suits your organisation depends mainly on what you want to keep in-house. You can find more articles on choices like these in our knowledge base.

Frequently asked questions

What is an API in one sentence?

An API is a set of agreements that lets two software systems request or send data to each other in a structured way, without a human in between.

What is the difference between an API and an API integration?

The API is the counter: the set of agreements a system offers. An API integration is the actual piece of software that connects system A's counter to system B's, so that data flows back and forth automatically.

What is the difference between REST and GraphQL?

REST returns a fixed response per endpoint (all fields of a resource). With GraphQL, the query determines which fields you get back, which is useful for complex data models. REST is the most widely used standard, while GraphQL is stronger for specific front-end or mobile scenarios.

How much does an API integration cost?

That depends on the number of systems, the complexity of the business logic, and the requirements around compliance and monitoring. A simple iPaaS integration sits at the low end of the spectrum; a production-grade multi-system integration with custom middleware costs considerably more. Always ask for a scoping conversation before requesting a quote.

Is an API integration GDPR-proof?

Not by itself; it has to be set up that way. With a DPA, TLS encryption, audit logging and data minimisation, an API integration can be fully GDPR-compliant. The responsibility lies with you as the data controller, together with your integration partner.

How secure is an API integration?

Secure once the basics are right: authentication via OAuth 2.0 or securely managed API keys, TLS on all traffic, no credentials in source code, rate limiting against abuse and monitoring for unusual patterns. Insecure as soon as one of those elements is missing.

How do I get started with an API integration?

Start with the question: what manual work are people doing now that could actually be automated? List which systems are involved, whether they have an API, and what the business value is. With that list, a first conversation with an integration partner becomes much more focused, and you can judge for yourself whether it should go via iPaaS or custom development.

How long does it take to build an API integration?

That varies a lot. A simple iPaaS flow between two common SaaS tools can be up and running in a few working sessions. A custom integration with multiple systems, field-level mapping, monitoring and compliance requirements takes a project of several sprints. Lead time is almost never the bottleneck; clarity about scope and access to the API credentials is.

What happens when an API changes?

SaaS vendors usually announce API changes well in advance. A good integration partner monitors those announcements, plans the migration and tests the upgrade path. Without structural maintenance, you often only discover a breaking change on the day the old version is switched off.

The key points.

01

An API is not a screen

It is a counter between software systems: structured data through requests and responses, without a UI.

02

Integration is the interplay

The connection of two or more APIs, with attention to authentication, rate limits, retries and monitoring.

03

iPaaS or custom

Standard flows with Zapier or Make, complex or business-critical logic with custom middleware.

Talk to us about your API integration?

A half-hour introduction. You tell us which systems you want to connect, and we'll share our thoughts straight away on architecture, approach and points of attention, with no sales pitch.

Edit content