Data exchange visual arrangement system and method based on API

Abstract

The invention provides a data exchange visual arrangement system and method based on an API, and relates to the technical field of API data processing and flow arrangement, and the system comprises a component library which is used for storing a plurality of reusable visual components, and each visual component corresponds to a conventional operation node in a third-party platform docking process; the arrangement grouping module is used for creating arrangement groups according to API arrangement requirements associated with functions and configuring a preprocessor and a postprocessor for the arrangement groups; the visual composer is used for associating each visual component with the corresponding preprocessor and the corresponding postprocessor according to the required visual component dragged from the component library by a developer and the quoted created composing group; and according to an execution sequence and a data flow direction of each visual component defined by a developer through a connection line, completing an API arrangement process and generating a data exchange process graph. The method has the beneficial effects that the third-party docking efficiency is greatly improved, and the docking threshold is greatly reduced.

Description

Technical Field

[0001] This invention relates to the field of API data processing and workflow orchestration technology, and in particular to an API-based data exchange visualization orchestration system and system. Background Technology

[0002] With the deepening of digital transformation, microservice architecture and distributed systems have become the mainstream forms of enterprise IT architecture. The widespread deployment of various business systems such as ERP, CRM, HRM, and SCM has made cross-system and cross-platform data exchange a core element supporting enterprise operations. As a standardized carrier for data interaction between different systems, APIs (Application Programming Interfaces) directly determine the collaborative efficiency of enterprise business processes and market responsiveness through their interface efficiency and management capabilities.

[0003] Currently, when enterprises exchange data with third-party platforms via APIs, they generally rely on traditional hard-coding development methods. However, with the increasing number of third-party platforms being connected and the rapid iteration of interface protocols, this development model has gradually exposed insurmountable technical bottlenecks, severely hindering the advancement of enterprise digitalization. Specifically, this manifests as follows: 1. Low Development Efficiency: The API interfaces of different third-party platforms exhibit significant heterogeneity in communication protocols (REST / SOAP / HTTP, etc.), authentication rules (OAuth2.0 / API Key / SAML, etc.), and data formats (JSON / XML / custom schema, etc.). Traditional development models require custom-written adaptation code for each platform. In this model, a large amount of repetitive work is concentrated on basic operations such as protocol parsing, authentication logic implementation, and data format conversion. Furthermore, due to the lack of reusable component-based resources, when new requirements for integrating with similar third-party platforms arise, similar code must still be written repeatedly. This causes the integration cycle to increase linearly with the number of platforms, severely slowing down the pace of business expansion.

[0004] 2. Poor Flexibility: Third-party platform APIs are not static; changes such as parameter adjustments, authentication method upgrades, and return format optimizations occur frequently. Traditional hard-coding methods completely solidify the interface logic in the source code, requiring developers to locate and modify even minor changes, followed by a series of processes including retesting, recompiling, and deployment. This rigid architecture cannot adapt to the dynamic changes of third-party platforms and struggles to meet the iterative needs of enterprise business processes. When enterprises need to add process branches or adjust data processing rules, they often need to refactor a large amount of code, resulting in extremely poor scalability.

[0005] 3. High Technical Barriers: Traditional API integration development involves complex technical details such as network protocols, encryption algorithms, and exception handling. It must be completed by backend developers with specialized backgrounds. Non-technical personnel, such as operations and product staff who are most familiar with business needs, are completely unable to participate in the design and adjustment of the integration process. When business departments raise requirements, such as optimizing the order data synchronization process, they must repeatedly communicate the details of the requirements with developers before coding implementation. This process is time-consuming and often results in discrepancies between the technical implementation and business requirements. This technical barrier leads to low efficiency in converting business needs into practical applications and also increases the workload of professional developers.

[0006] Therefore, there is an urgent need for a technical solution that can break through the limitations of the traditional hard-coding model, reduce the technical threshold for API data exchange through component reuse, visual orchestration, and standardized configuration, improve the efficiency of connection and change response capabilities, and achieve efficient collaboration between business needs and technical implementation. Summary of the Invention

[0007] To address the problems existing in the prior art, this invention provides an API-based data exchange visualization orchestration system, comprising: The component library stores multiple reusable visual components, each of which corresponds to a regular operation node in the process of connecting with a third-party platform. The orchestration grouping module is used to create orchestration groups for functionally related API orchestration requirements, and to configure pre-processors and post-processors for the orchestration groups; A visual orchestrator, connecting the component library and the orchestration grouping module, is used to associate each visual component with the corresponding pre-processor and post-processor based on the visual components dragged and dropped by the developer from the component library and the referenced orchestration groups, and to complete the API orchestration process and generate a data exchange flowchart based on the execution order and data flow direction of each visual component defined by the developer through connections.

[0008] Preferably, the visualization components include an input component, a condition judgment component, an API component, a variable aggregation component, an output component, and a sub-process component.

[0009] Preferably, the preprocessor includes an input preprocessor and an API preprocessor, and the postprocessor includes an API postprocessor and an output postprocessor.

[0010] Preferably, the visual orchestrator has preset global variables and provides a visual editing port for process variables; The visual orchestrator includes an orchestration module, which is used to construct a variable system based on the global variables referenced by the developers during the orchestration process and the process variables defined for each of the corresponding visual components through the visual editing port, and embed it into the data exchange flowchart.

[0011] Preferably, the global variable is configured to be available in all API orchestration processes, and the process variable is configured to be valid only within the lifecycle of the current API orchestration process.

[0012] Preferably, the global variable is configured to be read-only or require permission verification before it can be modified.

[0013] Preferably, the visualization orchestrator also provides a cache configuration port for developers to configure caching mechanisms and error retry mechanisms for the associated global variables and / or process variables of each visualization component; The caching mechanism includes an automatic refresh mechanism, a manual refresh mechanism, and an exception refresh mechanism. The automatic refresh mechanism is associated with a cache refresh cycle, the manual refresh mechanism is associated with a corresponding visual refresh port, and the exception refresh mechanism is associated with exception refresh conditions. The error retry mechanism includes the number of refreshes triggered by an error.

[0014] Preferably, it also includes an API orchestration execution engine connected to the visual orchestrator. The visual orchestrator further includes a compilation module for compiling the data exchange flowchart into a JSON format file and deploying it to the API orchestration execution engine. The API orchestration and execution engine is used to configure publishing information for the JSON format file and synchronize it to the configuration center of the API gateway to generate standardized API interfaces that directly provide services to the outside world.

[0015] Preferably, it also includes a process execution engine connected to the API gateway, used to load the JSON format file based on the data exchange process request, and to call the pre-processor before executing the API component in the visualization component, and then execute the API component to call the third-party platform interface to receive the returned result, thereby triggering the post-processor to output the returned result.

[0016] This invention also provides an API-based data exchange visualization orchestration method, applied to the aforementioned data exchange visualization orchestration system, wherein the data exchange visualization orchestration method includes: Step S1: The data exchange visualization orchestration system abstracts the regular operation nodes in the third-party platform integration process into reusable visualization components and stores them in the component library; Step S2: The data exchange visualization orchestration system creates orchestration groups for the functionally related API orchestration requirements, and configures a pre-processor and a post-processor for the orchestration groups. Step S3: The data exchange visualization orchestration system associates each visualization component with the corresponding pre-processor and post-processor based on the visualization components dragged and dropped by the developer from the component library and the referenced orchestration groups, and generates a data exchange flowchart based on the execution order and data flow direction of each visualization component defined by the developer through the connection.

[0017] The above technical solution has the following advantages or beneficial effects: 1) Significantly improves third-party integration efficiency: By "replacing coding with drawing," "batch adaptation in groups," and "process reuse," more than 90% of repetitive development work is reduced. Specifically, by pre-storing multiple visual components in the component library, routine operation nodes during third-party platform integration are encapsulated, eliminating the need for developers to repeatedly code; core functionality configuration can be completed simply by dragging and dropping. By creating orchestration groups and configuring pre-processors and post-processors, these components can be applied in batches to all API components within a group, avoiding the need to configure common logic for each component and improving the configuration efficiency of multi-API collaborative integration. Furthermore, developers can define the component execution order and data flow by connecting lines, eliminating the need to worry about code syntax and nested logic, thus shortening the third-party platform integration cycle from weeks to hours. 2) Extreme flexibility and scalability: When third-party platform interfaces change or business requirements are adjusted, only component configurations, group processors or process links need to be modified in the visual interface. No code changes are required. Adjustments, testing and release can be completed in a very short time, and changes can be responded to quickly. 3) Significantly lowers the barrier to entry: For simple data integration scenarios, data integration can be completed without the intervention of professional personnel. Attached Figure Description

[0018] Figure 1 A schematic diagram of the structure of an API-based data exchange visualization orchestration system is shown in a preferred embodiment of the present invention. Figure 2 In a preferred embodiment of the present invention, developers construct an interface diagram of the docking process by dragging and dropping visual components; Figure 3 This is a schematic diagram illustrating the hierarchical relationship and scope of global variables and process variables in a preferred embodiment of the present invention. Figure 4 A schematic diagram illustrating the scope of operation and calling order of processors in an orchestration group, as shown in a preferred embodiment of the present invention; Figure 5This is a flowchart illustrating a preferred embodiment of the present invention, illustrating a data exchange visualization orchestration method based on an API. Detailed Implementation

[0019] The present invention will now be described in detail with reference to the accompanying drawings and specific embodiments. The present invention is not limited to this embodiment; other embodiments that conform to the spirit of the present invention may also fall within the scope of the present invention.

[0020] In a preferred embodiment of the present invention, based on the above-mentioned problems existing in the prior art, an API-based data exchange visualization orchestration system is provided, such as... Figure 1 As shown, it includes: Component Library 1 is used to store multiple reusable visual components, each of which corresponds to a common operation node in the process of integrating with a third-party platform. Orchestration Grouping Module 2 is used to create orchestration groups for functionally related API orchestration requirements and to configure pre-processors and post-processors for orchestration groups; Visual orchestrator 3 connects component library 1 and orchestration grouping module 2. It is used to associate each visual component with the corresponding pre-processor and post-processor based on the visual components dragged and dropped by the developer from the component library and the referenced orchestration groups. It also completes the API orchestration process and generates a data exchange flowchart based on the execution order and data flow of each visual component defined by the developer through the connection.

[0021] Specifically, in this embodiment, before performing visual orchestration, common operation nodes in the third-party platform integration process are abstracted into reusable visual components and stored in component library 1. These components allow for direct drag-and-drop use and reuse, eliminating the tedious repetitive coding process of traditional development and reducing the amount of basic integration code by more than 90%. These visual components not only possess high reusability but also provide full functional coverage for different integration scenarios, specifically including: Input component: This is the starting point of the process, serving as the execution starting point for the API orchestration process. It allows you to define the process inputs, such as order number, transaction amount, and other process input parameters. Its standardized parameter configuration interface avoids the problem of chaotic parameter definitions in traditional development, providing a clear data entry point for subsequent process execution. Conditional judgment component: Implements process branch control based on variable values, supports multiple branches, and allows for visual configuration of judgment conditions through "variable + operator + value" (such as ${flow.success} == true), eliminating the need to write if-else code blocks, making process logic adjustments more intuitive and effectively improving the speed of responding to changes in business requirements; API component: Calls third-party data platform interfaces, supports protocols such as HTTP / HTTPS, and developers can directly configure the interface URL, request method, request header timeout, and number of retries in the configuration panel without having to worry about the underlying communication logic. The time to adapt to a new third-party interface is reduced from several hours to less than 5 minutes. Variable aggregation component: Provides advanced variable aggregation functionality, which can extract variables from upstream components to the variable aggregation component, and then use custom scripts (javascript) to process the data and export new variables for use by subsequent nodes. For example, it can aggregate order amount and tax variables into actual payment amount variable, avoiding redundant processing of data transfer between multiple components. Output component: As the endpoint of the API orchestration process, it defines the output of the process; in addition, a data encryption unit can be set to encrypt the output data with algorithms such as AES and RSA, and a data desensitization unit can be set to support the configuration of desensitization methods according to rules, such as masking sensitive information such as mobile phone numbers and ID card numbers, thus building data security protection from the component layer and meeting data security compliance requirements; Sub-process component: Referencing another component, the logic of the sub-process component is used as part of the current API orchestration process. That is, it supports referencing completed orchestration processes, and breaks down complex business logic into a modular structure of main process + sub-process. For example, the order status synchronization logic can be encapsulated as a sub-process and directly referenced in multiple main processes to achieve reuse and unified maintenance of process logic.

[0022] Furthermore, it also includes creating orchestration groups for API orchestration needs that interface with the same third-party platform or related functions, uniformly configuring pre-processors and post-processors, and achieving batch adaptation of common logic within the group. This completely solves the problem of repeatedly configuring the same rules for similar interfaces in traditional development, effectively improving the efficiency of multi-API collaborative integration. Its processor design precisely covers the common needs of each stage of the process. The pre-processors include: Input preprocessor: Called at the start of process execution, suitable for operations such as initial variables. For example, when connecting to a third-party platform, it is necessary to first obtain the connection certificate and store it as an initial variable for use by subsequent API components, avoiding repeated authentication logic coding.

[0023] API pre-processor: Called sequentially before each API component in a group, enabling automatic injection of common configurations. For example, it can inject common configurations or credentials for third-party integration, automatically adding "token" (${global.token}) to the API request header. This eliminates the need for manual configuration for each component, and batch synchronization can be achieved simply by modifying the processor rules when the token is updated.

[0024] The post-processor includes: API post-processors: These are invoked sequentially after each API component within a group, and are used to handle common logic in API return results. For example, when data returned by a third-party platform is in a uniform format, the post-processor can be configured with uniform logic to extract the data content.

[0025] Output post-processor: Called at the end of the process execution, suitable for operations such as result encryption, desensitization, and logging.

[0026] Building upon the aforementioned component library 1 and orchestration group creation, developers can utilize the graphical interface provided by the visual orchestrator 3 to construct third-party integration processes, such as... Figure 2 As shown, it specifically includes: Drag and drop the required visualization components (input components, API components, variable aggregation components, etc.) from Component Library 1 onto the canvas, and reference the created API orchestration group (the system automatically associates API components and processors within the group).

[0027] By connecting components, the execution order and data flow between them can be defined, variables can be passed, and business processes can be freely combined.

[0028] Once completed, a complete data exchange flowchart is generated, which can clearly and intuitively show the entire chain logic of third-party integration, effectively shortening the time for subsequent problem localization.

[0029] In a preferred embodiment of the present invention, the visual orchestrator 3 has a preset global variable and provides a visual editing port 31 for process variables; The visual orchestrator 3 includes an orchestration module 32, which is used to build a variable system based on the global variables referenced by developers during the orchestration process and the process variables defined for each corresponding visual component through the visual editing port 31, and embed it into the data exchange flowchart.

[0030] Specifically, in this embodiment, the aforementioned variable system is a core element of process execution, used for data transfer, context sharing, and dynamic calculation during process execution. This variable system consists of two main categories: global variables and process variables, and provides mechanisms such as variable aggregation, dynamic injection, and scope isolation.

[0031] 1. Global variables: such as Figure 3 As shown, global variables can be used in all API orchestration processes, have persistence and global uniqueness, and do not require additional definition within the process.

[0032] Typical examples include: system time (${global.systemTime}), API node information, environment parameters, gateway IP (${global.gatewayIp}), or custom variables.

[0033] 2. Process variables: such as Figure 3 As shown, it is generated by visualization components or defined by users, including fields returned by third-party interfaces, calculation results within the process, etc. Process variables are only effective within the lifecycle of the current orchestration process and are destroyed when the process is completed, thus achieving data scope isolation and avoiding interference between different processes.

[0034] 3. Variable aggregation: Supports calculation, concatenation, or transformation of multiple variables to generate new variables for use in subsequent processes.

[0035] 4. Variable injection and dynamic binding: Component configuration items support dynamic assignment through variable expressions.

[0036] 5. Variable security and isolation: Global variables are read-only or require permission verification before modification, and process variables are only valid for a single execution, effectively preventing data leakage and unauthorized tampering, and providing underlying support for data security.

[0037] For frequently called and stable data (such as basic configurations of third-party platforms, authentication information, etc.), caching and refresh strategies can be set. Specifically, the Visual Orchestrator 3 also provides a cache configuration port 33, which allows developers to configure the caching mechanism and error retry mechanism for the associated global variables and / or process variables of each visualization component. By reducing invalid calls and intelligent fault tolerance, the efficiency of process execution is effectively improved while reducing the exception rate. Caching mechanisms include: Automatic refresh mechanism: The automatic refresh mechanism is associated with a cache refresh cycle, such as 1 hour, which will automatically update when it expires; Manual refresh mechanism: The manual refresh mechanism is associated with a corresponding visual refresh port, which supports actively triggering cache updates in the visual interface; Error refresh mechanism: The error refresh mechanism is associated with error refresh conditions, such as when the process API call fails and cached data is used, the cache is forced to be refreshed.

[0038] The error retry mechanism includes the number of error-triggered refreshes. For example, if the number of error-triggered refreshes is set to 3, the number of errors is recorded when the process execution is abnormal (API timeout, return error code, variable aggregation failure). When the number of errors does not reach the threshold, the dependency cache is cleared and the process is re-executed; when the threshold is reached, retries are stopped and an error notification is triggered.

[0039] In a preferred embodiment of the present invention, an API orchestration execution engine 4 is further included, which is connected to a visual orchestrator 3. The visual orchestrator 3 further includes a compilation module 34, which is used to compile the data exchange flowchart into a JSON format file and deploy it to the API orchestration execution engine 4. API Orchestration Execution Engine 4 is used to configure publishing information for JSON format files and synchronize it to the configuration center of API Gateway 5 to generate standardized API interfaces that directly provide services to the outside world.

[0040] Specifically, in this embodiment, the visual orchestrator 3 compiles the constructed data exchange flowchart into a JSON format file that the backend can recognize, which fully defines the execution logic for third-party integration. This JSON format file is then deployed to the API orchestration execution engine 4 to complete the registration of the orchestration process. The registered process is a brand-new standardized API interface (referred to as "publish API"), enabling standardized reuse of the third-party integration process, including: Configure publishing information: Set the path to the publishing API (automatically generated or manually set) and access permissions (IP whitelist / Token verification).

[0041] Release storage: Synchronize the configuration and bound routes of the released API to the API gateway configuration center to generate standardized interfaces that can be directly provided to the outside world.

[0042] In a preferred embodiment of the present invention, a process execution engine 6 is further included, connected to an API gateway 5, for loading a JSON format file based on a data exchange process request, and calling a pre-processor before executing the API component in the visualization component, and then executing the API component to call a third-party platform interface to receive the returned result, thereby triggering the post-processor to output the returned result.

[0043] Specifically, in this embodiment, when a data exchange process request triggers a registered API orchestration process, the system will execute the following steps: 1. Request reception and route matching: Parse request parameters, match the corresponding published API configuration, and load the associated process JSON file.

[0044] 2. Execution preparation: Initialize process variables, load global variables, and check cache status (if a cache is configured, determine if it is valid).

[0045] 3. End-to-end execution: The gateway's interpretation and execution engine executes the logic step-by-step according to the JSON definition, such as... Figure 4 As shown: 3.1 Trigger the input component to verify the validity of the request parameters.

[0046] 3.2 Call the preprocessor of the group.

[0047] 3.3 Execute the API component, call the third-party platform interface, and receive the returned results.

[0048] 3.4 Triggering the post-processor of the group.

[0049] 3.5 Execute the variable aggregation component to generate process variables.

[0050] 3.6 Update the cache according to the caching rules (if configured).

[0051] Error handling: If an error occurs during execution, it will be handled according to the error mechanism configured above (retry, clear cache, trigger notification).

[0052] Result return: After execution, the output component is called (and the data encryption unit is triggered if encryption is required), and the final result (such as {"code": 200, "data": {"thirdOrderNo": "P20240520001", "payStatus": "pending"}}) is returned to the requester.

[0053] In summary, the API-based data exchange visualization orchestration system of this invention, through its innovative design of component-based reuse, grouped adaptation, and visualization orchestration, completely breaks through the limitations of traditional hard-coded development, achieving high efficiency, flexibility, and standardization in third-party platform integration. It includes: Significantly improve the efficiency of third-party integration: By "drawing instead of coding", "grouping and batch adaptation" and "process reuse", more than 90% of repetitive development work is reduced, and the integration cycle of third-party platforms is shortened from weeks to hours.

[0054] Extreme flexibility and scalability: When third-party platform interfaces change or business requirements are adjusted, you only need to modify component configurations, group processors or process links in the visual interface, without changing the code. Adjustments, testing and release can be completed in a very short time, and you can respond quickly to changes.

[0055] Significantly lowers the barrier to entry: For simple data integration scenarios, data integration can be completed without the intervention of professional personnel.

[0056] High stability and fault tolerance: The caching mechanism reduces repeated calls to third-party platforms and lowers interface pressure; error retry and cache clearing logic prevents the spread of anomalies, and the error notification mechanism ensures timely detection of problems and improves system stability.

[0057] End-to-end observability and easy maintenance: The graphical monitoring interface intuitively displays the business forms and execution status of third-party integrations, making problem localization clearer; standardized deployment reduces process maintenance costs and facilitates team collaboration.

[0058] Unified governance and security assurance: All third-party integration processes are managed uniformly through the API gateway, supporting unified configuration of security policies (IP whitelist, data encryption, and data anonymization) to meet data security compliance requirements.

[0059] This invention also provides an API-based data exchange visualization orchestration method, applied to the aforementioned data exchange visualization orchestration system, such as... Figure 5 As shown, the data exchange visualization orchestration method includes: Step S1: The data exchange visualization orchestration system abstracts the regular operation nodes in the process of connecting with third-party platforms into reusable visualization components and stores them in the component library; In step S2, the data exchange visualization orchestration system creates orchestration groups for the functionally related API orchestration requirements and configures pre-processors and post-processors for the orchestration groups. In step S3, the data exchange visualization orchestration system associates each visualization component with its corresponding pre-processor and post-processor based on the visualization components dragged and dropped by the developers from the component library and the referenced orchestration groups. It also generates a data exchange flowchart based on the execution order and data flow direction of each visualization component defined by the developers through connections.

[0060] The above description is merely a preferred embodiment of the present invention and does not limit the implementation and protection scope of the present invention. Those skilled in the art should realize that any equivalent substitutions and obvious changes made using the content of this specification and illustrations should be included within the protection scope of the present invention.

Claims

1. A data exchange visualization orchestration system based on API, characterized in that, include: The component library stores multiple reusable visual components, each of which corresponds to a regular operation node in the process of connecting with a third-party platform. The orchestration grouping module is used to create orchestration groups for functionally related API orchestration requirements, and to configure pre-processors and post-processors for the orchestration groups; A visual orchestrator, connecting the component library and the orchestration grouping module, is used to associate each visual component with the corresponding pre-processor and post-processor based on the visual components dragged and dropped by the developer from the component library and the referenced orchestration groups, and to complete the API orchestration process and generate a data exchange flowchart based on the execution order and data flow direction of each visual component defined by the developer through connections.

2. The data exchange visualization orchestration system according to claim 1, characterized in that, The visualization components include input components, condition judgment components, API components, variable aggregation components, output components, and sub-process components.

3. The data exchange visualization orchestration system according to claim 1, characterized in that, The preprocessor includes an input preprocessor and an API preprocessor, and the postprocessor includes an API postprocessor and an output postprocessor.

4. The data exchange visualization orchestration system according to claim 1, characterized in that, The visual orchestrator has preset global variables and provides a visual editing port for process variables; The visual orchestrator includes an orchestration module, which is used to construct a variable system based on the global variables referenced by the developers during the orchestration process and the process variables defined for each of the corresponding visual components through the visual editing port, and embed it into the data exchange flowchart.

5. The data exchange visualization orchestration system according to claim 4, characterized in that, The global variables are configured to be available in all API orchestration processes, while the process variables are configured to be valid only within the lifecycle of the current API orchestration process.

6. The data exchange visualization orchestration system according to claim 4, characterized in that, The global variable is configured to be read-only or requires permission verification before it can be modified.

7. The data exchange visualization orchestration system according to claim 4, characterized in that, The visual orchestrator also provides a cache configuration port for developers to configure caching mechanisms and error retry mechanisms for the associated global variables and / or process variables of each visual component. The caching mechanism includes an automatic refresh mechanism, a manual refresh mechanism, and an exception refresh mechanism. The automatic refresh mechanism is associated with a cache refresh cycle, the manual refresh mechanism is associated with a corresponding visual refresh port, and the exception refresh mechanism is associated with exception refresh conditions. The error retry mechanism includes the number of refreshes triggered by an error.

8. The data exchange visualization orchestration system according to claim 1, characterized in that, It also includes an API orchestration execution engine connected to the visual orchestrator. The visual orchestrator further includes a compilation module for compiling the data exchange flowchart into a JSON format file and deploying it to the API orchestration execution engine. The API orchestration and execution engine is used to configure publishing information for the JSON format file and synchronize it to the configuration center of the API gateway to generate standardized API interfaces that directly provide services to the outside world.

9. The data exchange visualization orchestration system according to claim 8, characterized in that, It also includes a process execution engine, which is connected to the API gateway and is used to load the JSON format file based on the data exchange process request. Before executing the API component in the visualization component, it calls the pre-processor, then executes the API component to call the third-party platform interface to receive the returned result, thereby triggering the post-processor to output the returned result.

10. A data exchange visualization orchestration method based on API, characterized in that, The data exchange visualization orchestration method, applied to the data exchange visualization orchestration system as described in any one of claims 1-9, comprises: Step S1: The data exchange visualization orchestration system abstracts the regular operation nodes in the third-party platform integration process into reusable visualization components and stores them in the component library; Step S2: The data exchange visualization orchestration system creates orchestration groups for the functionally related API orchestration requirements, and configures a pre-processor and a post-processor for the orchestration groups. Step S3: The data exchange visualization orchestration system associates each visualization component with the corresponding pre-processor and post-processor based on the visualization components dragged and dropped by the developer from the component library and the referenced orchestration groups, and generates a data exchange flowchart based on the execution order and data flow direction of each visualization component defined by the developer through the connection.

Images