What is an API integration, and why does it matter?

An API is a defined way for one piece of software to ask another for data or to make it do something. An integration uses APIs to connect your systems so data flows without retyping. The value is real; so is the dependency on someone else’s service.

By Nazar Kashuba · Reviewed

API stands for application programming interface. A payment provider, a CRM, a courier, a mapping service: each offers an API so that other software can use it.

What integrations give you

  • Data entered once appears where it is needed.
  • Fewer manual errors.
  • Processes that run without someone moving information by hand.
  • The ability to build on capabilities you would not want to build yourself.

What can go wrong

  • Changes. The other service updates or retires an API and your integration breaks.
  • Limits. Request limits, quotas and outages.
  • Data mismatches. Different systems define a customer or an order differently.
  • Security. Keys and permissions must be protected and limited to what is needed.
  • Costs. Some APIs are charged by use.

Before you depend on one

  1. Read the documentation and the terms, including how changes are announced.
  2. Check authentication, limits and what happens on errors.
  3. Decide what the system does when the other side is down.
  4. Log requests and failures so problems are visible.
  5. Keep the integration code in one place so it is easy to update.

A well-built integration is nearly invisible. A poorly built one is a source of mysterious data problems.

All questions