T/SAIA 016-2023 Active

Scope: This document specifies the terms and definitions, symbols and abbreviations, interface classification, security requirements, technical requirements, and data module API interfaces of the big data interface for the community financial cloud platform, as well as application scenario API data interfaces. This document is applicable to the design, development, and application of the big data interface for the community financial cloud platform. Main technical content: 7. Technical requirements 7.1 Requirements for interface message format 7.1.1 Unified user identification In the various systems of the community financial cloud, each user is assigned a unified object ID to avoid confusion when transferring user data across different systems. This document stipulates that each user must have a UUID as a unified user identifier. 7.1.2 Request message The request message consists of: a) Interface address: The URL of the interface request, which should include the name of the requested resource in the path. b) Request method: Use compliant GET, POST, and PUT methods. c) Request header: May include: — Additional information transmitted via the request, in the form of key-value pairs. — A content type declaration for the submitted data, such as "Content-type: application/json". — Request parameters: Contains one or more parameters for data retrieval, each consisting of a parameter name and corresponding value. These should only be used when the request method is GET. — Request body: Should contain the submitted data, and should only be used when the request method is POST or PUT. 7.1.3 Response message The response message consists of: a) Response result status line; b) Response header: May include: — Additional information transmitted via the response, in the form of key-value pairs. — A content type declaration for the submitted data, such as "Content-type: application/json". c) Response body: Should include: — Returned data