Application Programming Interface (API)

Technical explanation

An API specifies available operations, inputs, outputs, authentication, errors, and behavioural expectations. APIs may use HTTP, events, language-level calls, or other protocols. Good API design includes stable contracts, versioning, documentation, security, idempotency where required, and observability.

Business relevance

APIs enable connected products, partner ecosystems, automation, and modular architectures. Their quality directly affects integration speed, reliability, security, and the cost of change.

Implementation example

A CRM API lets an approved integration create leads, retrieve account details, and subscribe to change events using scoped credentials and documented rate limits.

Limitations and common misconceptions

An API does not guarantee interoperability or data quality. Poorly designed contracts create tight coupling, and exposed interfaces expand the attack surface. Compatibility and lifecycle management require ongoing ownership.

Topics

Sources