# Integration Publishing & Enablement — Integration Productization Cycle

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

Language: en

Entity ID: api-publishing

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

Read [shared station guidance](https://apiopscycles.com/stations/api-publishing.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 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)

## Journey exit criteria

- The solution passes quality, security, compliance, and readiness checks. — The API passes compliance, security, and audit checks. (ID: audit-passed)
- Audit findings and remediation decisions are shared with the relevant stakeholders. (ID: audit-reports-shared)
- The capability is ready to be published or released through the selected delivery mechanism. — The API is ready to be deployed and exposed through the intended gateways and environments. (ID: api-ready-for-publishing)
- Consumer-facing documentation and onboarding materials are ready. — Consumer-facing API documentation is complete enough for publishing and onboarding. (ID: api-documentation-ready)

## Description

Publish the integration capability so teams can discover it, evaluate it, request access, complete onboarding, reuse it, and get support.

## Role participation and responsibilities

- [Integration Architect](https://apiopscycles.com/roles/integration-architect.md) (lead): Designs integration approaches and implementation styles that connect the capability or API with other systems.
- [API Consumer Representative](https://apiopscycles.com/roles/api-consumer-specialist.md) (core): Represents the needs of developers, integrators, or other API consumers who use the API directly.
- [Documentation and DevRel Owner](https://apiopscycles.com/roles/api-devrel-specialist.md) (core): Owns onboarding content, developer communication, and documentation quality for API consumers.
- [Partner or Vendor Manager](https://apiopscycles.com/roles/partner-specialist.md) (core): Coordinates external partner, supplier, or vendor relationships that influence capability or API strategy and delivery.
- [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.
- [Compliance and Legal Specialist](https://apiopscycles.com/roles/compliance-specialist.md) (consulted): Clarifies legal, privacy, regulatory, and contractual requirements that affect the capability, API, interface, or automation.
- [Security Specialist](https://apiopscycles.com/roles/security-specialist.md) (consulted): Ensures security risks, controls, and trust boundaries are addressed throughout the API lifecycle.