# Integration Architecture & Platform Decisions — Integration Productization Cycle

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

Language: en

Entity ID: api-platform-architecture

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

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

- Capability opportunity is identified and documented. — Individual API opportunities are identified and documented. (ID: api-opportunity-documented)
- The capability addresses a clear business need and is reusable by its intended consumers. — The API meets a clear business need and is reusable for multiple API consumers. (ID: api-reusability)
- 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 capability value proposition has been validated with business and consumer stakeholders. — The API value proposition has been reviewed and validated with the relevant business and consumer stakeholders. (ID: value-prop-validated)
- Consumer segments are identified. — API consumer segments (internal and external) are identified. (ID: consumer-segments-identified)
- A high-level implementation roadmap is defined. — High-level roadmaps for API development are established. (ID: api-roadmap-defined)

## Journey exit criteria

- The capability addresses a clear business need and is reusable by its intended consumers. — The API meets a clear business need and is reusable for multiple API consumers. (ID: api-reusability)
- 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 capability value proposition has been validated with business and consumer stakeholders. — The API value proposition has been reviewed and validated with the relevant business and consumer stakeholders. (ID: value-prop-validated)
- Consumer segments are identified. — API consumer segments (internal and external) are identified. (ID: consumer-segments-identified)
- A high-level implementation roadmap is defined. — High-level roadmaps for API development are established. (ID: api-roadmap-defined)

## Description

Select the integration architecture, implementation style, and platform capabilities, taking account of constraints and the governance model.

## Role participation and responsibilities

- [Platform Architect](https://apiopscycles.com/roles/platform-architect.md) (lead): Guides platform, integration, scalability, and architecture decisions that shape how the capability or API is built and operated.; suggested-answer-owner: [Integration Architecture Decision Canvas](https://apiopscycles.com/resources/integration-architecture-decision-canvas.md)
- [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.
- [Platform Owner](https://apiopscycles.com/roles/platform-owner.md) (core): Owns platform capabilities, roadmap, operational model, and service expectations.
- [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.
- [API Architect](https://apiopscycles.com/roles/api-architect.md) (consulted): Owns API architecture, design principles, and interface contract quality.
- [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.

## Resources

- [Business Impact Canvas](https://apiopscycles.com/resources/business-impact-canvas.md)
- [Location Canvas](https://apiopscycles.com/resources/location-canvas.md)
- [Capacity Canvas](https://apiopscycles.com/resources/capacity-canvas.md)
- [Integration Architecture Decision Canvas](https://apiopscycles.com/resources/integration-architecture-decision-canvas.md)