API, interface, integration: what vendors mean

The words that appear in every sales conversation, what they commit a vendor to, and the questions that reveal whether an integration actually exists.

Full guide planned · 8 min read

The short version

An API means a system provides a defined way for another system to request or send information. It does not mean your two vendors have already built, tested, or support an integration between their products. When a salesperson says “we have an API,” the next question is: do you currently have a production integration with the system we already run, and who maintains it when either product updates?

Start here

If you read one thing on this subject, read this.

Official resourceNIST Computer Security Resource Center

Application Programming Interface (API) — definition

A neutral, citable definition of an API.

Why it matters

Useful to have in front of you when a contract says a system is 'API enabled'. That phrase commits a vendor to far less than most buyers assume.

Questions to ask your vendor

Take these into the meeting. A vendor who answers them clearly is one worth continuing with.

  1. Do you have a production integration with the exact system we run, at the version we run?
  2. Can we speak to a department using that integration in service?
  3. Is the API included in our license or priced separately?
  4. Is it documented and publicly available, or only accessible through your services team?
  5. When either product updates and the interface breaks, whose responsibility is it?

The full guide is still being written

What is above is the Hub’s framing and the best outside reading we could verify — useful on its own, and honest about being a starting point rather than the finished piece. If something here is wrong, or you know a better source, that is worth telling us before the long version is written.

Send a note