Skip to content
dvnt.io

Resources · glossary

API

An agreed way for one system to ask another for data or tell it to do something. APIs are how a shop knows its stock levels and how a website sends a contact to the CRM.

Also called
  • API
  • application programming interface
  • API integration
  • REST API
  1. 01

    Why the term comes up in every quote

    Because most of the cost of an integration is not in writing the code but in what the other side makes available. A system with a good API connects in days. A system without one needs workarounds, such as exchange files and manual exports, and those are what cause failures later.

  2. 02

    The first question before an integration

    Does the vendor of the other system have documentation and a test environment? Without either of the two, the quote becomes guesswork, because every detail only surfaces during the work.

  3. 03

    Limits people forget

    Many APIs limit the number of requests per minute or per day. With a thousand products this is no problem. With a hundred thousand it decides the architecture of the whole sync and whether stock levels are current every minute or once a night.

  4. 04

    Who owns the connection

    Agree whose access keys they are and who is responsible when the vendor changes the API. A change on the external system's side is not a fault in your site, but it stops it just as effectively.

In practice

Related terms

  • WebhookThe reverse of a normal request: the external system notifies yours itself when something happens. That way a payment status shows up instantly, without polling every minute.
  • DatabaseThe place where a system keeps its data in an organised form: products, orders, accounts, content. Everything else can be rebuilt; the database cannot.

← All terms

15 minutes. No sales pitch.

A term in a proposal sounds foreign? In 15 minutes we explain what it means for your project.