本文档定义了API生态系统的框架、功能和协议，该生态系统将支持在线同步交互。具体而言，该文件: -定义了开发API的逻辑和技术分层方法，包括转换规则。具体的逻辑模型（如ISO 20022模型）不包括在内，但它们将在特定场景中引用，以供指导； -将主要从REST设计的角度来考虑，但是会考虑其他的蓝图或场景提供的可替代的建筑风格（例如WebSoCo和Webhook）； -定义API的API生态系统设计原则、基于Web服务的API规则、数据有效负载和版本控制； -列出与API生态系统的安全、身份和注册相关的注意事项。具体的技术解决方案将不会被定义，但它们将在特定场景中被引用，以供指导； -定义除了查询/响应异步消息传递之外的体系结构使用，以发布/订阅来支持高级和现有的业务模型。 本文件不包括: -金融服务中API实现的具体技术规范； -开发基于ISO 20022特定消息格式的JSON API，如PAIN、CAMT和PACS； -由特定法律框架定义或确定的技术规范。

This document defines the framework, function and protocols for an API ecosystem that will enable online synchronised interaction. Specifically, the document: — defines a logical and technical layered approach for developing APIs, including transformational rules. Specific logical models (such as ISO 20022 models) are not included, but they will be referenced in the context of specific scenarios for guidance purposes; — will primarily be thought about from a RESTful design point of view, but will consider alternative architectural styles (such as WebSocket and Webhook) where other blueprints or scenarios are offered; — defines for the API ecosystem design principles of an API, rules of a Web-service-based API, the data payload and version control; — sets out considerations relevant to security, identity and registration of an API ecosystem. Specific technical solutions will not be defined, but they will be referenced in the context of specific scenarios for guidance purposes; — defines architectural usage beyond query/response asynchronous messaging towards publish/subscribe to support advanced and existing business models. This document does not include: — a specific technical specification of an API implementation in financial services; — the development of JSON APIs based on the ISO 20022 specific message formats, such as PAIN, CAMT and PACS; — a technical specification that is defined or determined by specific legal frameworks.