# Integration Readiness Assurance — Integration Productization Cycle

Canonical page: https://apiopscycles.com/cycles/integration-productization-cycle/stations/api-audit

Language: en

Entity ID: api-audit

Cycle: [Integration Productization Cycle](https://apiopscycles.com/cycles/integration-productization-cycle.md)

Read [shared station guidance](https://apiopscycles.com/stations/api-audit.md) first. The sections below supplement or replace the corresponding shared sections for this cycle. Sections not repeated here retain the shared guidance.

## Journey entry criteria

- The chosen architecture, platform, and implementation style have been validated with the relevant architecture, security, and platform stakeholders. — The chosen API architecture and platform patterns have been validated with the relevant architecture, security, and platform stakeholders. (ID: architecture-patterns-validated)
- The selected interface provides an appropriate abstraction for consumers. — The API is intended to shield consumers from backend complexity and inconsistencies. (ID: hide-backend-discrepancies)
- The interface design and exposed capabilities trace back to business value and consumer needs. — The API design and exposed capabilities clearly trace back to business value and user needs. (ID: design-reflects-business-value)
- The interface design follows agreed design standards and conventions. — The API design follows our shared API product and design conventions. (ID: api-consistency)

## Journey exit criteria

- The chosen architecture, platform, and implementation style have been validated with the relevant architecture, security, and platform stakeholders. — The chosen API architecture and platform patterns have been validated with the relevant architecture, security, and platform stakeholders. (ID: architecture-patterns-validated)
- The interface design and exposed capabilities trace back to business value and consumer needs. — The API design and exposed capabilities clearly trace back to business value and user needs. (ID: design-reflects-business-value)
- The interface and its capabilities are documented clearly enough for review, audit, and onboarding. — The API and its exposed capabilities are described clearly enough for review, audit, and onboarding. (ID: api-description-available)
- The interface design follows agreed design standards and conventions. — The API design follows our shared API product and design conventions. (ID: api-consistency)
- The interface contract has been validated and tested against functional and non-functional requirements. — The API contract is tested and meets functional and non-functional requirements. (ID: api-contract-tested)

## Description

Assure integration readiness, governance, quality, security, compliance, and operational evidence before release.

## Role participation and responsibilities

- [API Governance Owner](https://apiopscycles.com/roles/governance-specialist.md) (lead): Represents review, audit, and organization-wide governance practices for API quality and conformity.
- [Compliance and Legal Specialist](https://apiopscycles.com/roles/compliance-specialist.md) (core): Clarifies legal, privacy, regulatory, and contractual requirements that affect the capability, API, interface, or automation.
- [Integration Architect](https://apiopscycles.com/roles/integration-architect.md) (core): Designs integration approaches and implementation styles that connect the capability or API with other systems.
- [Security Specialist](https://apiopscycles.com/roles/security-specialist.md) (core): Ensures security risks, controls, and trust boundaries are addressed throughout the API lifecycle.
- [Support and Operations Owner](https://apiopscycles.com/roles/operations-specialist.md) (core): Represents runtime support, incident handling, observability, and operational readiness for the capability, API, or automation.
- [Business Owner](https://apiopscycles.com/roles/business-owner.md) (consulted): Represents business goals, funding, and expected outcomes for the capability, API, or automation initiative.
- [Delivery Engineer](https://apiopscycles.com/roles/api-engineer.md) (consulted): Owns implementation, automation, testing, and release flow concerns needed to deliver the capability, API, or automation reliably.
- [Platform Architect](https://apiopscycles.com/roles/platform-architect.md) (consulted): Guides platform, integration, scalability, and architecture decisions that shape how the capability or API is built and operated.