Skip to main content

API-First Design

Statement​

Every integration point is designed and agreed as an API contract before any implementation, UI, or batch process is built.

Rationale​

API-first prevents ad-hoc point-to-point integrations, reduces rework, and enables parallel development. It also makes capabilities reusable by future consumers.

Implications​

  • API specifications (OpenAPI/AsyncAPI) are reviewed and approved before development starts
  • APIs are published in the enterprise API catalogue
  • Breaking changes require a deprecation process