API calling method and device, electronic equipment, storage medium and program product

Abstract

The invention relates to the technical field of data processing, and provides an API calling method and device, electronic equipment, a storage medium and a program product, and the method comprises the steps: receiving an API access request sent by a data provider; analyzing a request parameter in the API access request to obtain at least one request field and a field value corresponding to each request field; determining a request entry parameter based on each request field, the field value corresponding to each request field and the data type of each field value; calling a target API of the data receiver based on the request incoming parameter, so as to send the request incoming parameter to the data receiver; the request input parameter is used for indicating the data receiver to execute the service logic matched with the request input parameter. According to the method and the device, time does not need to be wasted in connection adaptation of the data provider and the downstream data receiver, that is, the low-code integration platform only needs to analyze the API access request to automatically generate the request entry parameter capable of calling the target API, so that API calling is quickly realized, and the API calling efficiency is improved.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to an API calling method, device, electronic device, storage medium and program product. Background Art

[0002] With the continuous development of digital construction of enterprises, the business systems of enterprises may include various application systems such as research, production, supply, sales, and management. Therefore, in response to a business request, it may be necessary to call the APIs (Application Programming Interface) of multiple application systems. Since the time when the customer goes online determines the application of mainstream technologies, even for applications developed with the same technology stack, their interface styles are inconsistent. For the client, it needs multiple servers to respond to a business request. If the server is not compatible with the API request, it will cause problems such as call failure, error reporting, and incorrect return value. Therefore, the compatibility of API requests needs to be processed during the API call process.

[0003] Traditionally, in the high-code field, compatibility can be achieved as much as possible by using methods such as overloading, polymorphism, dynamic Json (JavaScript Object Notation) parsing, and direct reference to Map structures; however, learning the code is very complex and most of them are different, and it takes a lot of time to learn in order to implement service orchestration based on various codes. Therefore, for enterprises, the threshold for service orchestration through code is too high, which leads to low service orchestration efficiency and high service orchestration cost. Therefore, a low-code processing method is currently proposed.

[0004] Currently, although there is no need to learn code in the low-code field, due to the need for free references between services, time is wasted on the connection adaptation between the data provider and the downstream data receiver, and this connection adaptation requires manual settings to successfully call the target API of the data receiver. Therefore, the current API calling solution is inefficient and costly. Summary of the invention

[0005] The present invention aims to solve one of the technical problems existing in the prior art. To this end, the present invention proposes an API calling method, which does not need to waste time on the connection adaptation between the data provider and the downstream data receiver, that is, the low-code integration platform only needs to parse the API access request to automatically generate the request input parameters that can call the target API, thereby quickly realizing the API call, that is, improving the efficiency of the API call.

[0006] The invention also provides an API calling device, an electronic device, a storage medium and a program product.

[0007] The API calling method according to the first aspect of the present invention is applied to a low-code integration platform, and the method includes: Receive API access requests sent by data providers; Parsing request parameters in the API access request to obtain at least one request field and field values ​​corresponding to each of the request fields; Determine the request input parameter based on each of the request fields, the field value corresponding to each of the request fields, and the data type of each of the field values; The target API of the data recipient is called based on the request input parameter to send the request input parameter to the data recipient; the request input parameter is used to instruct the data recipient to execute business logic matching the request input parameter.

[0008] According to the API calling method of an embodiment of the present invention, an API access request sent by a data provider is received, request parameters in the API access request are parsed, at least one request field and field values ​​corresponding to each request field are obtained, and request input parameters are determined based on each request field, the field values ​​corresponding to each request field and the data type of each field value, so that the target API of the data recipient can be called directly based on the request input parameters to send the request input parameters to the data recipient, without wasting time on the connection adaptation between the data provider and the downstream data recipient. That is, the low-code integration platform only needs to parse the API access request to automatically generate request input parameters that can call the target API, thereby quickly realizing API calls, that is, improving the efficiency of API calls. In other words, the response speed of API access requests is improved, and this method does not require manual operation, thereby reducing the cost of API calls.

[0009] According to an embodiment of the present invention, the request parameter includes Json data; the Json data includes at least one request field and field values ​​corresponding to each of the request fields; After parsing the request parameters in the API access request, the method further includes: Determine the target hierarchical structure of the Json data; When the target hierarchical structure does not match the preset request input parameter hierarchical structure, an abnormal prompt message of request parameter error is returned to the data provider; In the case where the target hierarchical structure matches a preset request input parameter hierarchical structure, the step of determining the request input parameters based on each of the request fields, the field values ​​corresponding to each of the request fields, and the data type of each of the field values ​​is performed.

[0010] According to an embodiment of the present invention, before parsing the request parameters in the API access request, the method further includes: Obtaining an operation instruction acting on the interface configuration interface, and executing the operation instruction to determine the request input parameter hierarchical structure; Based on the request input parameter hierarchy structure, the input parameter fields of the backend service API are set so that the input parameter hierarchy structure of the backend service API is the same as the request input parameter hierarchy structure; the backend service API is an API that responds to API requests that match the request input parameter hierarchy structure.

[0011] According to one embodiment of the present invention, the backend service API is determined based on the following method: Determine, based on the target integration process, a backend service that responds to the API access request of the data provider; Based on the backend service, determining the backend service API; The target integration process is determined based on the following method: Obtaining a service orchestration instruction acting on a service orchestration interface, and executing an operation corresponding to the service orchestration instruction to perform service orchestration; Based on the service orchestration process determined by each service orchestration instruction, at least two backend services are integrated to obtain a target integration process; The target integration process is used to set the connection relationship between the at least two backend services.

[0012] According to an embodiment of the present invention, after returning the abnormal prompt information of the request parameter error to the data provider, the method further includes: Determine the number of times the abnormal prompt information is returned; Determine that the number of returns reaches a preset number threshold, and perform fuse processing on the API access request.

[0013] According to an embodiment of the present invention, calling a target API of a data recipient based on the request input parameter includes: Determine the target API that best matches the request input parameter from multiple APIs; If all input parameter fields of the target API match the request fields in the request input parameter, calling the target API based on the request input parameter; If there is a new request field in the request input parameter that does not match the input parameter fields of the target API, the input parameter fields of the target API are modified based on the new request field, and the target API with the modified input parameter fields is called based on the request input parameter.

[0014] According to an embodiment of the present invention, determining the target API that best matches the request input parameter from multiple APIs includes: If it is determined based on the stored mapping relationships that there is an API associated with the request input parameter, the API associated with the request input parameter among the multiple APIs is used as the target API that best matches the request input parameter; If it is determined based on several stored mapping relationships that there is no API associated with the request input parameter, multiple APIs are matched with the request input parameter to obtain the target API that best matches the request input parameter, and the mapping relationship between the request input parameter and the target API is persisted.

[0015] According to the second aspect of the present invention, the API calling device is deployed on a low-code integration platform, and the device includes: A request receiving module, used to receive API access requests sent by data providers; A parameter parsing module, used to parse the request parameters in the API access request to obtain at least one request field and field values ​​corresponding to each of the request fields; An input parameter determination module, used to determine the request input parameter based on each of the request fields, the field value corresponding to each of the request fields, and the data type of each of the field values; An API calling module is used to call the target API of the data recipient based on the request input parameters to send the request input parameters to the data recipient; the request input parameters are used to instruct the data recipient to execute business logic matching the request input parameters.

[0016] According to an embodiment of the third aspect of the present invention, an electronic device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, any one of the above-mentioned API calling methods is implemented.

[0017] According to the non-transitory computer-readable storage medium of the fourth aspect of the present invention, a computer program is stored thereon, and when the computer program is executed by a processor, the API calling method as described above is implemented.

[0018] A computer program product according to an embodiment of the fifth aspect of the present invention includes a computer program, which, when executed by a processor, implements any of the above-mentioned API calling methods.

[0019] The above one or more technical solutions in the embodiments of the present invention have at least one of the following technical effects: Receive the API access request sent by the data provider, parse the request parameters in the API access request, obtain at least one request field and the field values ​​corresponding to each request field, and determine the request input parameters based on each request field, the field values ​​corresponding to each request field and the data type of each field value, so that the target API of the data recipient can be called directly based on the request input parameters to send the request input parameters to the data recipient, without wasting time on the connection adaptation between the data provider and the downstream data recipient. That is, the low-code integration platform only needs to parse the API access request to automatically generate the request input parameters of the callable target API, thereby quickly realizing the API call, that is, improving the efficiency of the API call. In other words, it improves the response speed of the API access request, and this method does not require manual operation, thereby reducing the cost of API calls.

[0020] Additional aspects and advantages of the present invention will be given in part in the following description and in part will be obvious from the following description, or will be learned through practice of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] In order to more clearly illustrate the technical solutions in the present invention or the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0022] Figure 1 It is a flowchart of an API calling method provided by an embodiment of the present invention; Figure 2 is a schematic diagram of a service orchestration process provided by an embodiment of the present invention; Figure 3 It is a structural diagram of an API calling device provided by an embodiment of the present invention; Figure 4 It is a schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0023] In order to make the purpose, technical solution and advantages of the present invention clearer, the technical solution of the present invention will be clearly and completely described below in conjunction with the drawings of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0024] The present invention proposes the following embodiments. The API calling method provided by the embodiment of the present invention is described below in conjunction with the accompanying drawings. The execution subject of the API calling method is a low-code integration platform; the low-code integration platform can be an API gateway device, or a server, or a desktop computer, a laptop computer, etc., or a user's terminal, including but not limited to a mobile phone, a tablet computer, a PC (Personal Computer), a vehicle-mounted terminal, and a household smart appliance, etc.

[0025] This low-code integration platform is used for service orchestration, that is, application integration.

[0026] Figure 1 is a flowchart of an API calling method provided by an embodiment of the present invention, such as Figure 1 As shown, the API calling method includes: steps 110 to 140.

[0027] Step 110: Receive an API access request sent by a data provider.

[0028] Here, the data provider can be a client or a server. For example, initially receiving an API access request sent by a client, which requires multiple servers to respond, based on this, in order to achieve the final response, it is necessary to receive an API access request sent by a server in the middle of the process.

[0029] Here, the API access request is used to call the API (Application Programming Interface) of the data receiver (server) to respond to the API access request and return the response data to the data provider.

[0030] Step 120: parse the request parameters in the API access request to obtain at least one request field and field values ​​corresponding to each of the request fields.

[0031] Here, the request parameters include a request body, in which at least one request field and field values ​​corresponding to each request field may be transmitted in a Json data or form manner.

[0032] For example, the request parameters include Json data, and the Json data is {"name":"John","age":"30","id":"12345"}. Then, at least one request field obtained through parsing includes "name", "age" and "id". The field value corresponding to "name" is "John", the field value corresponding to "age" is "30", and the field value corresponding to "id" is "12345".

[0033] Step 130: Determine the request input parameters based on each of the request fields, the field values ​​corresponding to each of the request fields, and the data type of each of the field values.

[0034] Considering that the request input parameters of the called API not only require the field values ​​corresponding to each request field, but also the data type of each field value, it is necessary to determine the data type of each field value. In a specific embodiment, the field value is automatically analyzed to obtain the data type corresponding to the field value; for example, when parsing the request parameters, only "name": "John" is obtained, based on which its data type is determined as String, and "id": "12345", its data type is determined as Integer. Further, the data type of each field value is determined based on the context information of the request parameters. Further, the data type of the field value is determined based on the type of the field at the same level as the field value.

[0035] Step 140: Call the target API of the data recipient based on the request input parameter to send the request input parameter to the data recipient.

[0036] Here, the data receiver is the server that provides the target API, which is used to respond to the API access request. The target API is the API that matches the request input parameter, that is, the target API can be called based on the request input parameter.

[0037] It should be understood that the backend service of the data receiver has made compatibility adaptation through method overloading, Map parsing and other means, so that the target API can be called regardless of the request input parameters, that is, it supports non-fixed input parameters.

[0038] The request input parameter is used to instruct the data recipient to execute the business logic that matches the request input parameter. That is, the request input parameter is used to instruct the data recipient to complete the response process.

[0039] The API calling method provided by an embodiment of the present invention receives an API access request sent by a data provider, parses the request parameters in the API access request, obtains at least one request field and a field value corresponding to each request field, and determines the request input parameter based on each request field, the field value corresponding to each request field and the data type of each field value, so that the target API of the data recipient can be called directly based on the request input parameter to send the request input parameter to the data recipient, without wasting time on the connection adaptation between the data provider and the downstream data recipient. That is, the low-code integration platform only needs to parse the API access request to automatically generate the request input parameter of the callable target API, thereby quickly realizing the API call, that is, improving the efficiency of the API call. In other words, the response speed of the API access request is improved, and this method does not require manual operation, thereby reducing the cost of API calls.

[0040] Based on any of the above embodiments, in this method, the request parameter includes Json data; the Json data includes at least one request field and field values ​​corresponding to each of the request fields. That is, the request body in the request parameter transmits at least one request field and field values ​​corresponding to each of the request fields through Json data.

[0041] Accordingly, after parsing the request parameters in the API access request, the method further includes: Determine the target hierarchical structure of the Json data; When the target hierarchical structure does not match the preset request input parameter hierarchical structure, an abnormal prompt message of request parameter error is returned to the data provider; In the case where the target hierarchical structure matches a preset request input parameter hierarchical structure, the step of determining the request input parameters based on each of the request fields, the field values ​​corresponding to each of the request fields, and the data type of each of the field values ​​is performed.

[0042] In a specific embodiment, when the target hierarchical structure is inconsistent with the preset request input parameter hierarchical structure, the two do not match; if they are consistent, the two match.

[0043] It should be noted that each request field can be in different levels of the Json data. In order to call the target API, the target hierarchical structure of the Json data corresponding to the API access request should be determined and fixed, while the number of fields under the corresponding level can be uncertain, so that non-fixed input parameters can be supported.

[0044] In an embodiment of the present invention, the target hierarchical structure of the Json data and the request input parameter hierarchical structure pre-set by the low-code integration platform need to match each other. If the data provider modifies the hierarchical structure in the request, it will be predicted in advance that the target hierarchical structure does not match the pre-set request input parameter hierarchical structure, thereby returning an exception of incorrect request parameters, thereby completing the compatibility processing while ensuring the security of the API call, that is, making the request according to the pre-set request input parameter hierarchical structure.

[0045] In addition, it should be noted that the low-code integration platform will automatically convert the at least one parsed request field and the field values ​​corresponding to each request field, that is, automatically match the fields of the corresponding level, and record the non-fixed fields and their field values, so as to facilitate the subsequent determination of the request input parameters. During the storage process, at least one request field and the field values ​​corresponding to each request field can be stored through dynamic Json, or at least one request field and the field values ​​corresponding to each request field can be stored through a Map structure.

[0046] For example, the Json data looks like this: { "status": "success", "data": { "user": { "id": 12345, "name": "John Doe", "email": "john.doe@example.com", "profile": { "age": 30, "gender": "male", "address": { "street": "123 Main St", "city": "New York", "state": "NY", "zip": "10001" } }, "preferences": { "notifications": true, "newsletter": false } } }, "message": "Request processed successfully" } Among them, "status" and "data" are fields at the same level, and "user" is a field at the next level below "data".

[0047] The API calling method provided by the embodiment of the present invention parses the request parameters in the API access request, and when the target hierarchical structure does not match the preset request input parameter hierarchical structure, returns an exception prompt message of request parameter error to the data provider; when the target hierarchical structure matches the preset request input parameter hierarchical structure, executes the above step 130, thereby completing the compatibility processing while ensuring the security of the API call, that is, making the request according to the preset request input parameter hierarchical structure.

[0048] Based on any of the above embodiments, before the above step 120, the method further includes: Obtaining an operation instruction acting on the interface configuration interface, and executing the operation instruction to determine the request input parameter hierarchical structure; Based on the request input parameter hierarchy structure, the input parameter fields of the backend service API are set so that the input parameter hierarchy structure of the backend service API is the same as the request input parameter hierarchy structure; the backend service API is an API that responds to API requests that match the request input parameter hierarchy structure.

[0049] Here, the interface configuration interface is used to manually set the request input parameter hierarchy structure of the API, that is, to pre-set the request input parameter hierarchy structure through a visual interface configuration interface.

[0050] It should be noted that the API request input parameter hierarchy structure is pre-defined through the interface configuration interface, and at the same time, it is ensured that the backend service API of the data recipient has the same hierarchy structure, so that compatibility adaptation can be done in advance to support non-fixed input parameters.

[0051] Furthermore, common request fields can be pre-defined in the request input parameter hierarchy structure, and it is ensured that the backend service of the data recipient has been compatible and adapted through method overloading, Map parsing, etc., so as to support non-fixed input parameters.

[0052] The API calling method provided by the embodiment of the present invention obtains the operation instructions acting on the interface configuration interface, and executes the operation instructions to determine the request input parameter hierarchy structure, so that the setting of the request input parameter hierarchy structure can be completed without using code, that is, the setting is performed through a visual graphical interface, and there is no need to spend a lot of time learning the code. Users only need to focus on their own business needs, which further reduces the underlying redundant code development, helps to quickly and conveniently perform service orchestration, thereby lowering the threshold for service orchestration, improving the efficiency of service orchestration, and reducing the cost of service orchestration.

[0053] Based on any of the above embodiments, in this method, the backend service API is determined based on the following method: Determine, based on the target integration process, a backend service that responds to the API access request of the data provider; Based on the backend service, the backend service API is determined.

[0054] Here, the target integration process is used to indicate the connection relationship of the services, that is, the target integration process is used to indicate the connection relationship between the backend services of the data provider and the data receiver, so that based on the target integration process, the backend service that responds to the API access request of the data provider can be determined, and then the backend service API corresponding to the backend service can be determined.

[0055] The target integration process is determined based on the following method: Obtaining a service orchestration instruction acting on a service orchestration interface, and executing an operation corresponding to the service orchestration instruction to perform service orchestration; Based on the service orchestration process determined by each service orchestration instruction, at least two backend services are integrated to obtain a target integration process; The target integration process is used to set the connection relationship between the at least two backend services.

[0056] Here, the service orchestration interface is an interface for orchestrating choreographed components, which is used for users to orchestrate components based on the service orchestration interface. Specifically, it is used for users to trigger service orchestration instructions on the service orchestration interface. The service orchestration interface is a drawing interface for the service orchestration process, that is, a modeling interface for orchestration services.

[0057] The service orchestration interface may include but is not limited to one or more of the following: a flowchart drawing area, a component selection area, a connection selection area, a menu bar area, a shortcut operation area, a property configuration area, a debugging and version management panel, an interface configuration interface, etc., which is not specifically limited in the embodiment of the present invention.

[0058] The flowchart drawing area is used to draw the service orchestration flowchart, specifically, it is used to draw the flowchart of the technical route selected by the business needs. The flowchart drawing area is also used to visually configure the connection information of the service to which the API belongs, the API metadata definition, support inserting components, deleting components, connecting components, automatically generating connections, support text editing of component basic information, input and output parameter definitions, and support operations such as component copying, deleting, and skipping.

[0059] The component selection area is used to place various components. The component management area is divided into connector components, technical components, logic components, and trigger components. For example, in connector components, there are SaaS (Software as a Service) application connectors and enterprise self-built connectors; in technical components, there are data source components, message components, and ID (Identifier) ​​generator components; in logic components, there are parallel processing, conditional returns, loops, and conditional judgments; in trigger components, there are timer triggers, HTTP (HyperText Transfer Protocol) triggers, and message triggers. The components provided by the component management panel support selection in the flowchart drawing area.

[0060] Among them, the menu bar area provides global variable configuration, component connection configuration, and component definition function options for component assembly and connection configuration.

[0061] Among them, the quick operation area is used to place quick function options, which are used to provide quick editing functions for flowcharts, thereby improving the editing efficiency of flowcharts and supporting quick configuration instructions for the name, group management, and annotation description of the API service orchestration process.

[0062] Among them, the debugging and version management panel is used to respond to service orchestration testing and management instructions, including online debugging of the API service orchestration process, debugging log viewing, and orchestration process online, that is, historical version rollback.

[0063] Among them, the interface configuration interface is used to define the API request input parameter hierarchy structure, which can support automatic adjustment of input parameters and intelligent identification of request parameters according to the request, persist the API request parameters, and form different versions.

[0064] The property configuration area is used for property configuration, which can be used to configure the properties of components or connections.

[0065] Here, the service orchestration instruction is an instruction generated in response to the orchestration operation of the user through the execution subject of the embodiment of the present invention.

[0066] The service orchestration instruction can be triggered in all areas of the service orchestration interface. For example, in the flowchart drawing area, component dragging instructions, component customization instructions, text editing instructions, and component function operation instructions are triggered; in the component selection area, component replacement instructions, component click instructions, component configuration instructions, etc. are triggered; in the menu bar area, variable creation instructions, new configuration instructions, etc. are triggered; in the quick operation area, name modification instructions, group creation instructions, group selection instructions, etc. are triggered; in the debugging and version management panel, debugging instructions and version switching instructions are arranged.

[0067] The service orchestration instruction includes component operation instructions and other element operation instructions. The component operation instruction is used to operate the component to be operated. Specifically, the component operation instruction can be used to indicate the target component to be operated. For example, the indicated target component to be operated is a dragged component or a newly added component or a component to be connected or a component to be edited or a component to set the style content or a component to be configured, etc. Of course, the component operation instruction can also be used to indicate other operation information, which will not be described in detail here. The other element operation instruction is used to operate other elements besides components, such as lines, flow charts, direction arrows, grids, alignment lines, etc.

[0068] It should be noted that the service arrangement instruction can be triggered by clicking the display screen of the execution subject, or by an input device, which may include but is not limited to a mouse and a keyboard, etc. For example, the operation instruction is triggered according to various mouse events, or the operation instruction is triggered according to keyboard shortcuts.

[0069] The service orchestration instructions may include, but are not limited to, one or more of the following: component dragging instructions, line dragging instructions, component customization instructions, component line connection instructions, line direction determination instructions, text editing instructions, style operation instructions, component click instructions, line click instructions, component move instructions, flowchart click instructions, flowchart dragging instructions, flowchart setting instructions, flowchart zooming instructions, function click instructions, function dragging instructions, component property configuration instructions, line property configuration instructions, etc.

[0070] Specifically, executing operations corresponding to component dragging instructions, component customization instructions, text editing instructions, style operation instructions, or component attribute configuration instructions can provide components for the orchestration service, that is, to provide components selected by business needs. Executing operations corresponding to line dragging instructions, line direction determination instructions, style operation instructions, or line attribute configuration instructions can connect components, that is, to determine the orchestration route.

[0071] Specifically, the steps of obtaining the service orchestration instructions acting on the service orchestration interface several times and executing the operation corresponding to the service orchestration instructions are performed, and finally the service orchestration process is determined based on each service orchestration instruction, and the services of each target server are aggregated based on the graph data of the service orchestration process to obtain the target integration process. More specifically, the services of each target server indicated by the service orchestration process are determined, and the connection relationship between the services indicated by the service orchestration process is determined. Based on the connection relationship, the services of each target server are aggregated to obtain the target integration process.

[0072] For ease of understanding, Figure 2 As shown, the service orchestration process includes a first service, a second service and a third service. The first service and the second service are connected in parallel and then connected to the third service. Based on the service orchestration process, a first connection relationship between the first service and the second service is determined, and a second connection relationship between the first service and the second service and the third service is determined. Based on the first connection relationship and the second connection relationship, the first service, the second service and the third service are integrated and processed to obtain a target integration process of the three.

[0073] The API calling method provided in the embodiment of the present invention obtains the service orchestration instruction acting on the service orchestration interface, executes the operation corresponding to the service orchestration instruction, so as to perform service orchestration; based on the service orchestration process determined by each service orchestration instruction, at least two back-end services are integrated and processed to obtain the target integration process, and the API interoperability between multiple applications can be completed without using code, that is, the service orchestration is performed by means of a visual graphical interface, and there is no need to spend a lot of time learning the code. Users only need to focus on their own business needs, which further reduces the underlying redundant code development, helps to quickly and conveniently perform service orchestration, thereby lowering the threshold for service orchestration, improving the efficiency of service orchestration, and reducing the cost of service orchestration.

[0074] Based on any of the above embodiments, the component to be operated includes at least one of a service component, a data source component, and a message source component.

[0075] The data source may include but is not limited to: mysql, oracle, SQL Server, etc.

[0076] The API calling method provided in the embodiment of the present invention can orchestrate the services, data sources, and message sources of each server through the above-mentioned method to achieve interoperability between multiple systems of an enterprise.

[0077] Based on any of the above embodiments, after returning the abnormal prompt information of the request parameter error to the data provider, the method further includes: Determine the number of times the abnormal prompt information is returned; Determine that the number of returns reaches a preset number threshold, and perform fuse processing on the API access request.

[0078] Here, the return count is used to indicate the number of times the API access request cannot be responded to.

[0079] Here, the preset number threshold can be set according to actual needs, and the embodiment of the present invention does not make any specific limitation to this.

[0080] It should be noted that if an API access request is unresponsive for multiple consecutive times, the API access request will be automatically throttled, thereby avoiding the need to determine whether the target hierarchical structure matches the pre-set request input parameter hierarchical structure every time a request comes in, thereby further improving stability and further increasing response speed.

[0081] In one embodiment, it is determined whether the target hierarchical structure successfully matches the preset request input parameter hierarchical structure. If so, the API access request is restored.

[0082] The API calling method provided in the embodiment of the present invention determines that the number of times the abnormal prompt information is returned reaches a preset number threshold, and performs fuse processing on the API access request, thereby avoiding the need to determine whether it matches every time a request comes in, thereby further improving stability and further improving response speed.

[0083] Based on any of the above embodiments, in the method, calling a target API of a data receiver based on the request input parameter includes: Determine the target API that best matches the request input parameter from multiple APIs; If all input parameter fields of the target API match the request fields in the request input parameter, calling the target API based on the request input parameter; If there is a new request field in the request input parameter that does not match the input parameter fields of the target API, the input parameter fields of the target API are modified based on the new request field, and the target API with the modified input parameter fields is called based on the request input parameter.

[0084] It should be noted that if the target API of the data receiver that responds to the API access request cannot be determined, multiple APIs need to be polled to determine the target API that can be used to add the request input parameters. Alternatively, if the downstream data receiver provides multiple backend services, when it is uncertain to which API in the orchestration the request input parameters need to be added, the APIs of each downstream data receiver will be polled to match the request input parameters with the matching degree of multiple downstream APIs. Only when they are fully matched can the call and response relationship be determined.

[0085] Specifically, if all the input parameter fields of the target API match the request fields in the request input parameters, it means a complete match, and the target API can be called directly based on the request input parameters; if there are new request fields in the request input parameters that do not match the input parameter fields of the target API, it means an incomplete match, so the input parameter fields of the target API need to be modified.

[0086] That is to say, if no fully matching downstream API is found, the input parameter fields will be modified according to the API with the highest matching degree. Furthermore, according to the position of the new request field in the request input parameter, the new request field is also added to the target API to ensure that the two are consistent.

[0087] Furthermore, the mapping relationship between the request input and the target API is persisted, so that it is easy to directly determine the target API that best matches the request input, thereby improving the efficiency of API calls.

[0088] It should be understood that considering that the integration flow needs to predefine the input and output parameter structures, it is extremely difficult to implement dynamic parameter processing in the prior art. However, the embodiments of the present invention can dynamically support input parameters, connect the data provider with the downstream data receiver, and improve the compatibility of low-code service orchestration for this scenario.

[0089] The API calling method provided by the embodiment of the present invention determines the target API that best matches the request input parameters from multiple APIs. If the input parameter fields of the target API match the request fields in the request input parameters, the target API is called based on the request input parameters. If there are new request fields in the request input parameters that do not match the input parameter fields of the target API, the input parameter fields of the target API are modified based on the new request fields, and the target API with the modified input parameter fields is called based on the request input parameters. This allows support for non-fixed input parameters, and the API call can be successfully completed even if the request input parameters corresponding to the API access request have not appeared before; and can dynamically support input parameters, connecting data providers with downstream data receivers, thereby improving the compatibility of low-code service orchestration for this scenario.

[0090] Based on any of the above embodiments, in the method, determining the target API that best matches the request input parameter from multiple APIs includes: If it is determined based on the stored mapping relationships that there is an API associated with the request input parameter, the API associated with the request input parameter among the multiple APIs is used as the target API that best matches the request input parameter; If it is determined based on several stored mapping relationships that there is no API associated with the request input parameter, multiple APIs are matched with the request input parameter to obtain the target API that best matches the request input parameter, and the mapping relationship between the request input parameter and the target API is persisted.

[0091] Specifically, persisting the mapping relationship of the target API to the request entry means saving the mapping relationship to a non-volatile storage medium (such as a disk, a database, or a file system, etc.) to ensure that the mapping relationship can be directly obtained later. For example, the mapping relationship is saved from a temporary storage (such as a memory) to a non-volatile storage medium.

[0092] In a specific embodiment, the mapping relationship between the request input and the target API is stored in a database, and a fast index is established based on a hash table, so that the mapping relationship can be persisted and efficiently called.

[0093] Since the fields and structures involved in the request input parameters are fixed rather than dynamic most of the time, the request input parameters that have been called in the past will be re-circulated and matched in the next request, which will cause performance problems. Based on this, after completing the first normal call, the mapping relationship between the request input and the target API is persisted, so that in the next call of the same type, the downstream API can be directly called to avoid resource consumption caused by repeated matching. That is, the information of the determined request input parameters and the API corresponding to which backend service is saved for subsequent direct input response.

[0094] The API calling method provided by the embodiment of the present invention, if it is determined based on several stored mapping relationships that there is no API associated with the request input parameter, multiple APIs are matched with the request input parameter to obtain the target API that best matches the request input parameter, and the mapping relationship between the request input parameter and the target API is persisted; if it is determined based on several stored mapping relationships that there is an API associated with the request input parameter, the API associated with the request input parameter among the multiple APIs is used as the target API that best matches the request input parameter, that is, after completing the first normal call, the mapping relationship between the request input parameter and the target API is persisted, so that in the next call of the same type, the target API can be directly called, thereby improving the efficiency of API calls and avoiding resource consumption caused by repeated matching.

[0095] Furthermore, the above API calling method can also be implemented through the following embodiments.

[0096] Specifically, the highly compatible low-code API call is closely integrated with the connector definition module. More specifically, it involves application connector development, including connector metadata definition, connector execution action development (including configuration development, orchestration development), and connector response configuration definition. By defining the execution action of the application connector, orchestrating the development request parameters, and smoothing the data conversion and authentication gaps in the call process, the purpose of improving the efficiency of API microservice gateway orchestration development is achieved.

[0097] Specifically, the connection configuration definition is used to determine the connection configuration parameters when the API is called, and supports the default connection configuration including the connection address, connection protocol, proxy host and port. It supports connector developers to add connection configuration parameters, determine the field key, and then the caller configures the input parameters of the corresponding key.

[0098] In the connector, it is necessary to define the metadata of the highly compatible API in advance, define the input / output parameter structure hierarchy of the API, and support the use of URL (Uniform Resource Locator) and label marking for the same business implementation. This type of interface definition is called "execution action". Execution actions support configuration development and orchestration development. For configuration development, it refers to the native interface development of the API, and orchestration development is the pre-processing of the atomic interface. What is advanced is that this pre-processing can complete the authentication information of the atomic interface, as well as data encryption, data allergy, and data conversion logic in the connector in advance when requesting, reducing the risk of external exposure and improving the security of the connector interface.

[0099] Specifically, orchestration development supports the use of the system's own logical orchestration capabilities, combined with logical processors and technology connectors for visual orchestration, reducing the complexity of atomic service aggregation and improving ease of use.

[0100] In addition, the atomic interface of the connector, that is, the execution action, provides private / public management capabilities, and the connector developer manages the exposed interface and private interface to improve the flexibility of interface management. Among them, the private interface can be used in the orchestration development to meet the needs of the connector atomic interface aggregation. The public interface can be used in the integration flow to meet the aggregation needs of the multi-application integration orchestration development.

[0101] Response configuration serves as a unified response code management device for atomic interfaces in connectors, and plays a role in unified API response code management for enterprises.

[0102] In the connector development interface, you can preview the effects of all atomic APIs of the connector. This innovation allows you to view the parameters and data structure of the API when it is called without calling the connector, which can greatly improve the efficiency of connector development in the actual development process.

[0103] For the aggregated atomic services, the platform provides the ability to automatically generate APIs and API documents. This innovation is designed to improve API development efficiency. At the same time, the internal logic arrangement of the atomic services and the externally exposed APIs are linked and verified to ensure that the online APIs can be adjusted, reducing the troubleshooting process and complexity.

[0104] In addition, it provides the matching relationship between the upstream dynamic API and the downstream service API, and supports Json echo of the API input and output parameters (view the actual Json format of the input and output parameters), which is convenient for verifying interface parameters and improving verification efficiency.

[0105] Improve API development efficiency through flexible request input and output parameter input methods. In the embodiment of the present invention, a highly compatible API call method is proposed to automatically generate request input parameters for service orchestration based on the Json of the upstream API, but the method of quickly generating API request parameters is not limited to Map input parameters, TEXT input parameters, data table input parameters, reference to the previous node input parameters, import of Swagger document input parameters, and Swagger open interface input parameters, so as to achieve fast entry of API input and output parameters and dynamic API compatibility. Specifically, as shown below: 1) Import Json in the specified format and automatically generate request input and output parameters in the logic arrangement. More than 10 data formats are provided, and the json content is automatically verified and matched.

[0106] 2) Enter the parameter name, parameter type, and parameter description in text format, and automatically match the format to enter the parameter at the specified level.

[0107] 3) By referencing the data table in the database, identify the specified fields in the data table as the data format, parameter type and parameter description of the input parameter.

[0108] 4) By referencing the previous node, which generally contains parameters of an array structure or a normal structure, the parameters of the current node are copied to achieve fast entry of input and output parameters.

[0109] 5) Automatically generate input and output parameters of multiple API interfaces by importing the prepared Swagger document. This type of document introduces dependent packages in the code, edits the corresponding annotations and automatically generates documents in the specified format by using its component capabilities.

[0110] In addition, the input parameters support overwriting and appending. Overwriting means erasing all the original parameters and generating a new parameter structure, while appending allows users to append parameters under or after the specified node.

[0111] Specifically, in the case of array type, the appended form is to increase the parameters of the array node. In the case of common type parameters, the newly added parameters are appended after it.

[0112] This platform provides API path consistency management capabilities and reasonably groups atomic aggregate services to meet the scenario requirements of quickly identifying the ownership of atomic services when integrating multiple business systems.

[0113] Specifically, after creating an API service, developers can manage the API by adding groups. The prefix of the call link is preset in the group, and the developer supplements the URL of the group and assembles the specific address of the interface to form the complete path of the API. In addition, when creating a group, the API credentials are bound to achieve authentication of the group API.

[0114] It should be noted that there are two ways to authenticate APIs in the industry, namely, authenticating a single API and authenticating an API group. Authentication of a single API will lead to the problem that the overall authentication management of the business system cannot be aligned with the authentication method. The present invention selects the group authentication method, manages APIs by group, and manages the authentication credentials of the group to achieve the purpose of unified API access credentials for the specified system.

[0115] The API calling device provided by the present invention is described below. The API calling device described below and the API calling method described above can be referenced to each other.

[0116] Figure 3 is a schematic diagram of the structure of an API calling device provided by an embodiment of the present invention, such as Figure 3 As shown, the API calling device includes: a request receiving module 310, a parameter parsing module 320, an input parameter determining module 330 and an API calling module 340.

[0117] The request receiving module 310 is used to receive an API access request sent by a data provider.

[0118] The parameter parsing module 320 is used to parse the request parameters in the API access request to obtain at least one request field and field values ​​corresponding to each of the request fields.

[0119] The input parameter determination module 330 is used to determine the request input parameters based on each of the request fields, the field values ​​corresponding to each of the request fields, and the data type of each of the field values.

[0120] The API calling module 340 is used to call the target API of the data recipient based on the request input parameter to send the request input parameter to the data recipient; the request input parameter is used to instruct the data recipient to execute the business logic matching the request input parameter.

[0121] The API calling device provided by an embodiment of the present invention receives an API access request sent by a data provider, parses the request parameters in the API access request, obtains at least one request field and a field value corresponding to each request field, and determines the request input parameter based on each request field, the field value corresponding to each request field and the data type of each field value, so that the target API of the data recipient can be called directly based on the request input parameter to send the request input parameter to the data recipient, without wasting time on the connection adaptation between the data provider and the downstream data recipient. That is, the low-code integration platform only needs to parse the API access request to automatically generate the request input parameter of the callable target API, thereby quickly realizing the API call, that is, improving the efficiency of the API call. In other words, the response speed of the API access request is improved, and this method does not require manual operation, thereby reducing the cost of API calls.

[0122] Based on any of the above embodiments, the request parameter includes Json data; the Json data includes at least one request field and a field value corresponding to each of the request fields; the device also includes: A hierarchy determination module, used to determine the target hierarchy structure of the Json data; A prompt return module is used to return an abnormal prompt message of a request parameter error to the data provider when the target hierarchical structure does not match the preset request input parameter hierarchical structure; A step execution module is used to execute the step of determining the request input parameters based on each of the request fields, the field values ​​corresponding to each of the request fields, and the data type of each of the field values ​​when the target hierarchical structure matches the preset request input parameter hierarchical structure.

[0123] Based on any of the above embodiments, the device further includes: An instruction acquisition module is used to acquire an operation instruction acting on the interface configuration interface and execute the operation instruction to determine the hierarchical structure of the request input parameter; A field setting module is used to set each input parameter field of the backend service API based on the request input parameter hierarchy structure so that the input parameter hierarchy structure of the backend service API is the same as the request input parameter hierarchy structure; the backend service API is an API that responds to API requests that match the request input parameter hierarchy structure.

[0124] Based on any of the above embodiments, the device further includes: an API determination module; the API determination module is used to: Determine, based on the target integration process, a backend service that responds to the API access request of the data provider; Based on the backend service, the backend service API is determined.

[0125] The device further includes: a process determination module, which is used to: Obtaining a service orchestration instruction acting on a service orchestration interface, and executing an operation corresponding to the service orchestration instruction to perform service orchestration; Based on the service orchestration process determined by each service orchestration instruction, at least two backend services are integrated to obtain a target integration process; The target integration process is used to set the connection relationship between the at least two backend services.

[0126] Based on any of the above embodiments, the device further includes: A times determination module, used to determine the times of returning the abnormal prompt information; The request fuse module is used to determine whether the number of returns reaches a preset number threshold and to perform fuse processing on the API access request.

[0127] Based on any of the above embodiments, the API calling module 340 is further used to: Determine the target API that best matches the request input parameter from multiple APIs; If all input parameter fields of the target API match the request fields in the request input parameter, calling the target API based on the request input parameter; If there is a new request field in the request input parameter that does not match the input parameter fields of the target API, the input parameter fields of the target API are modified based on the new request field, and the target API with the modified input parameter fields is called based on the request input parameter.

[0128] Based on any of the above embodiments, the API calling module 340 is further used to: If it is determined based on the stored mapping relationships that there is an API associated with the request input parameter, the API associated with the request input parameter among the multiple APIs is used as the target API that best matches the request input parameter; If it is determined based on several stored mapping relationships that there is no API associated with the request input parameter, multiple APIs are matched with the request input parameter to obtain the target API that best matches the request input parameter, and the mapping relationship between the request input parameter and the target API is persisted.

[0129] Figure 4 An example of a physical structure diagram of an electronic device is shown in FIG. Figure 4As shown, the electronic device may include: a processor 410, a communication interface 420, a memory 430 and a communication bus 440, wherein the processor 410, the communication interface 420 and the memory 430 complete mutual communication through the communication bus 440. The processor 410 may call the logic instructions in the memory 430 to execute the API calling method, which includes: receiving an API access request sent by a data provider; parsing the request parameters in the API access request to obtain at least one request field and a field value corresponding to each of the request fields; determining the request input parameter based on each of the request fields, the field value corresponding to each of the request fields and the data type of each of the field values; calling the target API of the data recipient based on the request input parameter to send the request input parameter to the data recipient; the request input parameter is used to instruct the data recipient to execute the business logic matching the request input parameter.

[0130] In addition, the logic instructions in the above-mentioned memory 430 can be implemented in the form of a software functional unit and can be stored in a computer-readable storage medium when it is sold or used as an independent product. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc. Various media that can store program codes.

[0131] On the other hand, the present invention also provides a computer program product, which includes a computer program, which can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can execute the API calling method provided by the above methods, which includes: receiving an API access request sent by a data provider; parsing the request parameters in the API access request to obtain at least one request field and a field value corresponding to each request field; determining the request input parameter based on each request field, the field value corresponding to each request field and the data type of each field value; calling the target API of the data recipient based on the request input parameter to send the request input parameter to the data recipient; the request input parameter is used to instruct the data recipient to execute business logic matching the request input parameter.

[0132] On the other hand, the present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, is implemented to execute the API calling method provided by the above-mentioned methods, the method comprising: receiving an API access request sent by a data provider; parsing the request parameters in the API access request to obtain at least one request field and a field value corresponding to each of the request fields; determining the request input parameter based on each of the request fields, the field value corresponding to each of the request fields and the data type of each of the field values; calling the target API of the data recipient based on the request input parameter to send the request input parameter to the data recipient; the request input parameter is used to instruct the data recipient to execute business logic matching the request input parameter.

[0133] The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative labor.

[0134] Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be implemented by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.

[0135] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention.

[0136] The above embodiments are only used to illustrate the present invention, but not to limit the present invention. Although the present invention is described in detail with reference to the embodiments, it should be understood by those skilled in the art that various combinations, modifications or equivalent substitutions of the technical solutions of the present invention do not depart from the spirit and scope of the technical solutions of the present invention, and should be included in the scope of the claims of the present invention.

Claims

1. An API calling method, characterized in that: Applied to a low-code integration platform, the method includes: Receive API access requests sent by data providers; Parsing request parameters in the API access request to obtain at least one request field and field values ​​corresponding to each of the request fields; Determine the request input parameter based on each of the request fields, the field value corresponding to each of the request fields, and the data type of each of the field values; The target API of the data recipient is called based on the request input parameter to send the request input parameter to the data recipient; the request input parameter is used to instruct the data recipient to execute business logic matching the request input parameter.

2. The API calling method according to claim 1, characterized in that: The request parameter includes Json data; the Json data includes at least one request field and field values ​​corresponding to each of the request fields; After parsing the request parameters in the API access request, the method further includes: Determine the target hierarchical structure of the Json data; When the target hierarchical structure does not match the preset request input parameter hierarchical structure, an abnormal prompt message of request parameter error is returned to the data provider; In the case where the target hierarchical structure matches a preset request input parameter hierarchical structure, the step of determining the request input parameters based on each of the request fields, the field values ​​corresponding to each of the request fields, and the data type of each of the field values ​​is performed.

3. The API calling method according to claim 2, characterized in that: Before parsing the request parameters in the API access request, the method further includes: Obtaining an operation instruction acting on the interface configuration interface, and executing the operation instruction to determine the request input parameter hierarchical structure; Based on the request input parameter hierarchy structure, the input parameter fields of the backend service API are set so that the input parameter hierarchy structure of the backend service API is the same as the request input parameter hierarchy structure; the backend service API is an API that responds to API requests that match the request input parameter hierarchy structure.

4. The API calling method according to claim 3, characterized in that: The backend service API is determined based on the following method: Determine, based on the target integration process, a backend service that responds to the API access request of the data provider; Based on the backend service, determining the backend service API; The target integration process is determined based on the following method: Obtaining a service orchestration instruction acting on a service orchestration interface, and executing an operation corresponding to the service orchestration instruction to perform service orchestration; Based on the service orchestration process determined by each service orchestration instruction, at least two backend services are integrated to obtain a target integration process; The target integration process is used to set the connection relationship between the at least two backend services.

5. The API calling method according to claim 2, characterized in that: After returning the abnormal prompt information of the request parameter error to the data provider, the method further includes: Determine the number of times the abnormal prompt information is returned; Determine that the number of returns reaches a preset number threshold, and perform fuse processing on the API access request.

6. The API calling method according to claim 1, characterized in that: The calling of the target API of the data receiver based on the request input parameter includes: Determine the target API that best matches the request input parameter from multiple APIs; If all input parameter fields of the target API match the request fields in the request input parameter, calling the target API based on the request input parameter; If there are new request fields in the request input parameters that do not match the input parameter fields of the target API, the input parameter fields of the target API are modified based on the new request fields, and the target API with the modified input parameter fields is called based on the request input parameters.

7. The API calling method according to claim 6, characterized in that: Determining the target API that best matches the request input parameter from the multiple APIs includes: If it is determined based on the stored mapping relationships that there is an API associated with the request input parameter, the API associated with the request input parameter among the multiple APIs is used as the target API that best matches the request input parameter; If it is determined based on several stored mapping relationships that there is no API associated with the request input parameter, multiple APIs are matched with the request input parameter to obtain the target API that best matches the request input parameter, and the mapping relationship between the request input parameter and the target API is persisted.

8. An API calling device, characterized in that: Deployed on a low-code integration platform, the device includes: A request receiving module, used to receive API access requests sent by data providers; A parameter parsing module, used to parse the request parameters in the API access request to obtain at least one request field and field values ​​corresponding to each of the request fields; An input parameter determination module, used to determine the request input parameter based on each of the request fields, the field value corresponding to each of the request fields, and the data type of each of the field values; An API calling module is used to call the target API of the data recipient based on the request input parameters to send the request input parameters to the data recipient; the request input parameters are used to instruct the data recipient to execute business logic matching the request input parameters.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the API calling method according to any one of claims 1 to 7 is implemented.

10. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the API calling method according to any one of claims 1 to 7 is implemented.

11. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the API calling method according to any one of claims 1 to 7 is implemented.

Images