API management method and device, computer equipment, storage medium and program product

Abstract

The invention relates to an API management method and device, computer equipment, a storage medium and a program product. The method comprises the following steps: in response to an API search request of an API demander, obtaining an API search record of the API demander and an API interaction record between the API demander and each API developer; according to the API search record, the API interaction record and API demand information in the API search request, selecting a recommended API from the tradable APIs of the API management platform; and displaying the API description information of the recommended API to an API demand side. By adopting the method, the API can be well managed.

Description

Technical Field

[0001] The present application relates to the field of computer technologies, and particularly to an API management method, apparatus, computer device, storage medium, and program product. Background Art

[0002] With the rapid development of the Internet, APIs (Application Programming Interface) have become an important way for data exchange and service collaboration between developers and enterprises.

[0003] Currently, there are still many problems in the construction and management of the API ecosystem, such as the lack of unified standards for API management and trust issues in API transactions. Summary of the Invention

[0004] Based on this, in view of the above technical problems, it is necessary to provide an API management method, apparatus, computer device, storage medium, and program product that can achieve good management of APIs.

[0005] In a first aspect, the present application provides an API management method, which includes:

[0006] In response to an API search request from an API requester, obtain the API search record of the API requester and the API interaction records between the API requester and each API developer;

[0007] According to the API search record, API interaction record, and API requirement information in the API search request, select recommended APIs from the tradable APIs in the API management platform;

[0008] Display the API description information of the recommended APIs to the API requester.

[0009] In one embodiment, selecting recommended APIs from the tradable APIs in the API management platform according to the API search record, API interaction record, and API requirement information in the API search request includes:

[0010] Determine API requirement supplementary information according to the API search record and API interaction record; use the API requirement supplementary information to supplement the API requirement information in the API search request to obtain API global requirement information; select recommended APIs from the tradable APIs in the API management platform according to the API global requirement information.

[0011] In one embodiment, after displaying the API description information of the recommended APIs to the API requester, the method further includes:

[0012] Based on the API description information of the recommended API by the API requester, perform a selection operation on the recommended API to select the API to be traded from the recommended APIs; control the API requester and the API developer corresponding to the API to be traded to conduct API trading based on the API to be traded.

[0013] In one embodiment, it includes:

[0014] In response to a monitoring request for a target API initiated by any API developer, when the API developer is the developer of the target API, obtain the usage record and usage evaluation information of the target API; send the usage record and usage evaluation information of the target API to the API developer; receive the updated version of the target API from the API developer and store the updated version of the target API; wherein, the updated version is obtained by the API developer upgrading the target API based on the usage record and usage evaluation information of the target API.

[0015] In one embodiment, it includes:

[0016] When it is detected that any API is abnormal, send a rollback request to the API developer corresponding to the API; wherein, the rollback request includes the historical version information of the API; receive the rollback version information feedback by the API developer of the API based on the rollback request; roll back the API based on the rollback version information.

[0017] In one embodiment, according to the API global demand information, selecting recommended APIs from the tradable APIs of the API management platform includes:

[0018] Select recommended APIs from the tradable APIs of the API management platform according to the API global demand information and the API level of the API requester; wherein, the API level is determined based on the API certificate and API learning record of the API requester.

[0019] In a second aspect, the present application also provides an API management device, and the device includes:

[0020] An acquisition module, configured to, in response to an API search request of an API requester, acquire the API search record of the API requester and the API interaction record between the API requester and each API developer;

[0021] A selection module, configured to select recommended APIs from the tradable APIs of the API management platform according to the API search record, the API interaction record, and the API demand information in the API search request;

[0022] A display module, configured to display the API description information of the recommended APIs to the API requester.

[0023] In a third aspect, the present application further provides a computer device, including a memory and a processor. The memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0024] In response to an API search request from an API requester, obtain the API search record of the API requester and the API interaction records between the API requester and each API developer;

[0025] According to the API search record, the API interaction record, and the API requirement information in the API search request, select a recommended API from the tradable APIs in the API management platform;

[0026] Display the API description information of the recommended API to the API requester.

[0027] In a fourth aspect, the present application further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented:

[0028] In response to an API search request from an API requester, obtain the API search record of the API requester and the API interaction records between the API requester and each API developer;

[0029] According to the API search record, the API interaction record, and the API requirement information in the API search request, select a recommended API from the tradable APIs in the API management platform;

[0030] Display the API description information of the recommended API to the API requester.

[0031] In a fifth aspect, the present application further provides a computer program product, including a computer program. When the computer program is executed by a processor, the following steps are implemented:

[0032] In response to an API search request from an API requester, obtain the API search record of the API requester and the API interaction records between the API requester and each API developer;

[0033] According to the API search record, the API interaction record, and the API requirement information in the API search request, select a recommended API from the tradable APIs in the API management platform;

[0034] Display the API description information of the recommended API to the API requester.

[0035] The above API management method, device, computer device, storage medium and program product obtain the API search records of the API requester and the API interaction records between the API requester and each API developer by responding to the API search request of the API requester, realizing the acquisition of multi-dimensional information; further, recommended APIs can be selected from the tradable APIs of the API management platform according to the API search records, API interaction records, and API requirement information in the API search request, laying a foundation for accurately recommending APIs to the API requester; finally, the API description information of the recommended APIs is displayed to the API requester. This solution provides a way to analyze the API requirements of the API requester from multiple perspectives by introducing API search records and API interaction records, and lays a foundation for improving the success rate of API transactions; moreover, based on the API search records, API interaction records, and API requirement information in the API search request, accurate recommendation of APIs is realized, and finally good management of APIs is achieved. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the following will briefly introduce the drawings required for use in the description of the embodiments or related technologies. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0037] Figure 1 It is an application environment diagram of an API management method provided in an embodiment of the present application;

[0038] Figure 2 It is a schematic flowchart of an API management provided in an embodiment of the present application;

[0039] Figure 3 It is a schematic flowchart of selecting and recommending APIs provided in an embodiment of the present application;

[0040] Figure 4 It is a schematic flowchart after presenting the recommended APIs to the API requester provided in an embodiment of the present application;

[0041] Figure 5 It is a schematic flowchart of another API management method provided in an embodiment of the present application;

[0042] Figure 6 It is a structural block diagram of an API management device provided in an embodiment of the present application;

[0043] Figure 7 It is an internal structure diagram of a computer device provided in an embodiment of the present application. Detailed implementation manners

[0044] In order to make the objectives, technical solutions and advantages of the present application clearer and more understandable, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0045] The API management method provided by the embodiment of the present application can be applied to an application environment as Figure 1 shown. Among them, the terminal 102 communicates with the server 104 through a network. The data storage system can store the data that the server 104 needs to process. The data storage system can be integrated on the server 104, or can be placed in the cloud or on other network servers. The API requester can initiate an API search request through the terminal 102. Furthermore, the server 104 can respond to the API search request of the API requester, obtain the API search record of the API requester, and the API interaction record between the API requester and each API developer, and select a recommended API from the tradable APIs of the API management platform according to the API search record, the API interaction record, and the API requirement information in the API search request; finally, display the API description information of the recommended API to the API requester through the terminal 102. Among them, the terminal 102 can be, but is not limited to, various personal computers, laptop computers, smart phones, tablet computers, Internet of Things devices and portable wearable devices. The Internet of Things devices can be smart speakers, smart TVs, smart air conditioners, smart vehicle-mounted devices, etc. The portable wearable devices can be smart watches, smart bracelets, head-mounted devices, etc. The server 104 can be implemented by an independent server or a server cluster composed of multiple servers.

[0046] In an exemplary embodiment, as Figure 2 shown, an API management method is provided. Taking the method applied to the Figure 1 server 104 as an example for description, it can include the following steps:

[0047] S201, in response to the API search request of the API requester, obtain the API search record of the API requester, and the API interaction record between the API requester and each API developer.

[0048] Among them, the API search record can include, but is not limited to, information such as the identity identifier of the API requester, historical search keywords, and historical search time; the API interaction record can include, but is not limited to, information such as the identity identifier of the API requester, the identity identifier of the API developer, the communication information and transaction information between the API requester and each API developer.

[0049] Exemplarily, the API requester can enter a search keyword in the search box of the API management platform through the terminal 102 and click the search button to send an API search request to the server 104 via an HTTP request (such as GET or POST). Further, after receiving the API search request sent by the API requester, the server 104 will query the API search records of the API requester and the API interaction records between the API requester and each API developer according to the identity identifier of the API requester to determine the APIs that the API requester may be interested in and make accurate recommendations.

[0050] S202. Select recommended APIs from the tradable APIs in the API management platform according to the API search records, API interaction records, and API requirement information in the API search request.

[0051] Among them, the API search records may include, but are not limited to, information such as the identity identifier of the API requester, historical search time, and historical search keywords, etc.; the API requirement information may include, but is not limited to, information such as the identity identifier of the API requester, search keyword, and search time, etc.; the tradable APIs may represent the APIs that are available for the API requester to trade and are functioning properly; the recommended APIs may represent the APIs recommended according to the preferences or requirements of the API requester.

[0052] Exemplarily, the concerns, demand trends, usage habits, etc. of the API requester can be understood according to the historical search keywords in the API search records, the communication records and transaction records in the API interaction records, and the search keywords in the API requirement information. Further, the APIs that meet the requirements such as the concerns, demand trends, and usage habits of the API requester can be screened out from each tradable API. Optionally, the function descriptions of each tradable API in the API management platform, the API documents of each tradable API (the performance indicators, stability conditions, error handling mechanisms, etc. of each tradable API can be determined), and the charging information of each tradable API, etc. can be queried to select the APIs that meet the needs of the API requester, that is, the recommended APIs.

[0053] S203. Display the API description information of the recommended APIs to the API requester.

[0054] Among them, the API description information may include, but is not limited to, API function description, technical specifications (such as supported HTTP methods, content types, encodings, etc.), API usage description, and API charging information, etc.

[0055] Exemplarily, the recommended APIs can be sorted according to the concerns, demand trends, usage habits, etc. of the API demand side, so as to determine the order and position of presenting each recommended API to the API demand side (such as customizing a personalized recommendation plan); further, each recommended API can be directly presented to the API demand side through the terminal 102 (presenting description information such as the API function description, technical specifications, API usage description, and API charging information of each recommended API), for the API demand side to browse and trade each recommended API, etc.

[0056] The above API management method obtains the API search records of the API demand side and the API interaction records between the API demand side and each API developer in response to the API search request of the API demand side, realizing the acquisition of multi-dimensional information; further, recommended APIs can be selected from the tradable APIs of the API management platform according to the API search records, API interaction records, and API demand information in the API search request, laying a foundation for accurately recommending APIs to the API demand side; finally, the API description information of the recommended APIs is presented to the API demand side. This solution provides a way to analyze the API demands of the API demand side from multiple perspectives by introducing API search records and API interaction records, and lays a foundation for improving the success rate of API transactions; moreover, based on the API search records, API interaction records, and API demand information in the API search request, accurate recommendation of APIs is realized, and finally good management of APIs is achieved.

[0057] Based on the above embodiments, the embodiments of the present application supplement the functions of the API management platform. The API management platform includes various types of APIs, from basic data interfaces to complex service interfaces. In order to trade each API, it can include functions such as API registration, release, search, classification, review, and transaction; further, in order to promote the reuse and collaboration of APIs, the API management platform can provide API quality evaluation, user evaluation, and comment functions to help enterprises and developers better manage and use APIs; further, the embodiments of the present application also explain the above embodiment S202 in detail. Specifically, the process of selecting recommended APIs involved in the embodiments of the present application is as Figure 3 shown, and specifically includes the following steps:

[0058] S301, determine API demand supplementary information according to the API search records and API interaction records.

[0059] Among them, the API demand supplementary information can represent the potential demands of the API demand side; optionally, the API demand supplementary information can be different from the search keywords in the API demand information and can supplement the API demand information.

[0060] Exemplarily, historical search keywords in the API search records can be extracted, and the frequencies and combinations of the historical search keywords can be analyzed to identify the potential needs and potential interest points of the API requesters; and the communication information and transaction information in the API interaction records can be extracted to analyze information such as the usage habits and demand changes of the API requesters; furthermore, information such as the potential needs, potential interest points, usage habits, and demand changes of the API requesters can be determined as API demand supplementary information, or the repeatedly occurring demand information can be determined based on the potential needs, potential interest points, usage habits, and demand changes of the API requesters, and the repeatedly occurring demand information can be determined as API demand supplementary information.

[0061] S302. Use the API demand supplementary information to supplement the API demand information in the API search request to obtain the API global demand information.

[0062] Among them, the API global demand information can comprehensively represent the demands of the API requesters.

[0063] Exemplarily, based on the API demand information in the PI search request, the API demand supplementary information can be traversed, and the information that does not repeat the API demand information in the API demand supplementary information can be determined, and the information that does not repeat the API demand information in the API demand supplementary information and the API demand information can be merged to obtain the API global demand information, that is, the API global demand information is the demand information that integrates the API demand supplementary information and the API demand information.

[0064] S303. Select the recommended APIs from the tradable APIs in the API management platform according to the API global demand information.

[0065] One implementable way is to select the recommended APIs from the tradable APIs in the API management platform according to the API global demand information and the API level of the API requester.

[0066] Among them, the API level is determined based on the API certificate and API learning records of the API requester.

[0067] Optionally, to encourage API developers to share API usage experiences, technical problems, and solutions, etc., the API management platform provides API developers with some tools and resources such as API documents and sample codes to promote communication and collaboration among API developers. Moreover, to stimulate the creativity and learning enthusiasm of API developers and improve the quality and usage effects of APIs, the API management platform provides API development competitions, API technology sharing sessions, and API training courses, etc. Furthermore, API certificates can be obtained through professional API competitions and can also be obtained by participating in the API development competitions of the API management platform, and the API certificates obtained by API demanders can be added to personal information. API learning records can represent the learning records of API demanders participating in the training courses of the API management platform.

[0068] Exemplarily, according to the API global demand information, an API that meets the API demand of the API demander can be selected from the tradable APIs of the API management platform. Further, according to the API level of the API demander, an API that matches the API level of the API demander can be selected again from the APIs that meet the API demand of the API demander, that is, the recommended API.

[0069] Optionally, the API level can represent factors such as the business scale, technical capabilities, and dependence on APIs of the API demander.

[0070] In the embodiments of the present application, by introducing API demand supplementary information, a data basis is provided for obtaining API global demand information, and finally a foundation is laid for comprehensively evaluating the API demand of API demanders.

[0071] Based on the above embodiments, the embodiments of the present application further explain the above embodiment S203 in detail. Specifically, the embodiments of the present application involve the process after presenting the API description information of the recommended API to the API demander, as Figure 4 shown, which specifically includes the following steps:

[0072] S401, according to the selection operation of the API demander on the recommended API based on the API description information of the recommended API, select the API to be traded from the recommended APIs.

[0073] Among them, the API to be traded can represent the API for which the API demander conducts a transaction.

[0074] Exemplarily, the API requester browses and selects the recommended APIs through the terminal 102, carefully compares the API description information of each recommended API, including the detailed descriptions of its functions, performance, security, compatibility, and usage conditions, etc., as well as the performance metrics of each recommended API, evaluates the performance metrics such as the response time, throughput, and concurrent processing ability of each recommended API, and finally selects the API to be traded that meets the API requirements from the recommended APIs.

[0075] S402, control the API requester and the API developer corresponding to the API to be traded to conduct API trading based on the API to be traded.

[0076] Exemplarily, the specific details of the API trading can be clarified to the API requester and the API developer corresponding to the API to be traded, including but not limited to the API name, API identifier, function description, performance metrics, price, usage terms and conditions, etc.; further, through the API management platform, the API requester and the API developer corresponding to the API to be traded can sign a trading agreement to clarify their respective rights and obligations, including key terms such as the usage scope, term, data security, and privacy protection of the API.

[0077] Optionally, before signing the trading agreement, the API requester can test the API to be traded (such as performance testing, security auditing, and compatibility checking, etc.) to ensure that it meets the business requirements.

[0078] In the embodiments of the present application, by elaborating the process of API trading in detail, ideas are provided for the API management platform to provide an API trading market.

[0079] Based on the above embodiments, the process of updating the target API in the embodiments of the present application specifically includes the following steps:

[0080] In response to a monitoring request for the target API initiated by any API developer, in the case where the API developer is the developer of the target API, obtain the usage record and usage evaluation information of the target API; send the usage record and usage evaluation information of the target API to the API developer; receive the updated version of the target API from the API developer, and store the updated version of the target API.

[0081] Wherein, the updated version is obtained by the API developer upgrading the target API based on the usage record and usage evaluation information of the target API.

[0082] Exemplarily, for any API developer, when the API developer trades the target API developed by it on the API management platform, a monitoring request for the target API can be sent to the API management platform, that is, the usage records and usage evaluation information of the target API can be regularly sent to the API developer, so that the API developer developing the target API can timely understand the problems existing in the actual use of the target API; furthermore, based on the problems existing in the actual use of the target API, the API developer developing the target API can choose whether to update and upgrade the target API to overcome the existing problems of the current target API; if the API developer developing the target API chooses to update the target API and uploads the updated version to the API management platform for API requesters to trade.

[0083] Optionally, the API management platform also provides functions such as version release control (to ensure that API requesters can select suitable API versions), version rollback (after the API is released, if serious problems are found in the API, the API product can be rolled back to the previous version), version dependency management (a technical means to effectively manage the external libraries, modules, services or resources on which the API depends), and compatibility detection (to ensure that the API can run normally and be compatible with other software and hardware in different operating systems, browsers, devices, etc.), to achieve centralized management of API versions, ensure the stability and compatibility of the API, and avoid the problem of chaotic API version management; furthermore, it also provides API version change notifications and migration guides for API developers to help API requesters timely update and adapt to the new version of the API, and can also implement the gray release and A / B test functions of API versions.

[0084] In the embodiment of the present application, by monitoring the target API, it provides a direction and idea for updating the target API and lays a foundation for providing a more perfect API for API requesters.

[0085] Based on the above embodiments, the process of rolling back the API in the embodiment of the present application specifically includes the following steps:

[0086] When it is detected that any API is abnormal, a rollback request is sent to the corresponding API developer of the API.

[0087] Among them, the rollback request includes the historical version information of the API; receiving the rollback version information fed back by the API developer of the API based on the rollback request; and rolling back the API based on the rollback version information.

[0088] Exemplarily, the API management platform can regularly check the status of APIs by monitoring tools (such as Prometheus, Grafana, etc.) or custom scripts, and can also monitor APIs by using evaluation information; furthermore, when any API anomaly is detected, the anomaly handling logic can be triggered; optionally, the API name and API identifier of the anomalous API can be identified, and the contact information of the API developer who developed the anomalous API (such as the email of the API development team, etc.) can be obtained, and a rollback request including detailed anomaly information (such as error time, error type, error log, etc.) can be sent to the API developer of the anomalous API; furthermore, the sending status of the rollback request can be recorded, and the response and rollback progress of the developer can be tracked to ensure that the anomaly problem is resolved.

[0089] In the embodiments of the present application, by rolling back the anomalous API, the normal use of the API requester is ensured, and the continuity of the API service is achieved.

[0090] Based on the above embodiments, this embodiment provides an alternative example of an API management method. As Figure 5 shown, the specific implementation process is as follows:

[0091] S501, in response to the API search request of the API requester, obtain the API search record of the API requester and the API interaction records between the API requester and each API developer.

[0092] It should be noted that in response to a monitoring request for a target API initiated by any API developer, when the API developer is the developer of the target API, obtain the usage record and usage evaluation information of the target API; send the usage record and usage evaluation information of the target API to the API developer; receive the updated version of the target API from the API developer, and store the updated version of the target API; wherein, the updated version is obtained by the API developer upgrading the target API based on the usage record and usage evaluation information of the target API.

[0093] S502, determine the API requirement supplementary information according to the API search record and the API interaction records.

[0094] S503, use the API requirement supplementary information to supplement the API requirement information in the API search request to obtain the API global requirement information.

[0095] S504, select a recommended API from the tradable APIs of the API management platform according to the API global requirement information and the API level of the API requester.

[0096] Among them, the API level is determined based on the API certificate and API learning record of the API requester.

[0097] S505, display the API description information of the recommended API to the API requester.

[0098] S506, select the API to be traded from the recommended APIs according to the selection operation of the recommended API by the API requester based on the API description information of the recommended API.

[0099] It should be noted that in the case where any API is detected to be abnormal, a rollback request is sent to the API developer corresponding to the API; among them, the rollback request includes the historical version information of the API; receive the rollback version information fed back by the API developer of the API based on the rollback request; perform a rollback on the API based on the rollback version information.

[0100] S507, control the API requester and the API developer corresponding to the API to be traded to perform an API transaction based on the API to be traded.

[0101] The specific processes of the above S501 - S507 can refer to the description of the method embodiments above. Their implementation principles and technical effects are similar, and will not be elaborated here.

[0102] It should be understood that although the steps in the flowcharts involved in the above - mentioned embodiments are shown in sequence according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless there is a clear description in this article, the execution of these steps has no strict order limit, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above - mentioned embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily executed at the same moment, but can be executed at different moments, and the execution order of these steps or stages is not necessarily sequential, but can be executed alternately or in turn with at least a part of other steps or steps or stages in other steps.

[0103] Based on the same inventive concept, the embodiments of the present application also provide an API management device for implementing the above - mentioned API management method. The solution provided by this device to solve problems is similar to the solution described in the above method. Therefore, the specific limitations in one or more of the following API management device embodiments can refer to the limitations on the API management method in the above text, and will not be elaborated here.

[0104] In an exemplary embodiment, as Figure 6 shown, an API management device 1 is provided, including: an acquisition module 10, a selection module 20, and a display module 30, where:

[0105] An obtaining module 10, configured to obtain an API search record of an API requester and API interaction records between the API requester and each API developer in response to an API search request of the API requester.

[0106] A selection module 20, configured to select a recommended API from the tradable APIs in the API management platform according to the API search record, the API interaction records, and the API requirement information in the API search request.

[0107] A display module 30, configured to display API description information of the recommended API to the API requester.

[0108] In one embodiment, the selection module 20 is specifically configured to:

[0109] Determine API requirement supplementary information according to the API search record and the API interaction records; use the API requirement supplementary information to supplement the API requirement information in the API search request to obtain API global requirement information; and select a recommended API from the tradable APIs in the API management platform according to the API global requirement information.

[0110] In one embodiment, the API management device 1 further specifically includes:

[0111] A trading module, configured to select a to-be-traded API from the recommended APIs according to a selection operation of the API requester on the API description information of the recommended API; and control the API requester and the API developer corresponding to the to-be-traded API to perform an API transaction based on the to-be-traded API.

[0112] In one embodiment, the API management device 1 further specifically includes:

[0113] An API update module, configured to obtain a usage record and usage evaluation information of a target API in the case that an API developer is the developer of the target API in response to a monitoring request for the target API initiated by any API developer; send the usage record and usage evaluation information of the target API to the API developer; receive an updated version of the target API from the API developer, and store the updated version of the target API; wherein the updated version is obtained by the API developer upgrading the target API based on the usage record and usage evaluation information of the target API.

[0114] In one embodiment, the API management device 1 further specifically includes:

[0115] A rollback module, configured to send a rollback request to the API developer corresponding to an API when any abnormality of the API is detected; wherein, the rollback request includes historical version information of the API; receive rollback version information fed back by the API developer of the API based on the rollback request; and roll back the API based on the rollback version information.

[0116] In one embodiment, the selection module 20 is further specifically configured to:

[0117] Select a recommended API from the tradable APIs of the API management platform according to the API global requirement information and the API level of the API requester; wherein, the API level is determined based on the API certificate of the API requester and the API learning record.

[0118] Each module in the above API management device can be implemented in whole or in part by software, hardware, and their combination. Each of the above modules can be embedded in the processor of the computer device in hardware form or independent of it, or stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to each of the above modules.

[0119] In an exemplary embodiment, a computer device is provided. The computer device can be a server, and its internal structure diagram can be as Figure 7 shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, abbreviated as I / O), and a communication interface. Among them, the processor, the memory, and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store API data. The input / output interface of the computer device is used to exchange information between the processor and external devices. The communication interface of the computer device is used to communicate with external terminals through a network connection. When the computer program is executed by the processor, it implements an API management method.

[0120] Those skilled in the art can understand that Figure 7 the structure shown in

[0121] In an exemplary embodiment, a computer device is provided, including a memory and a processor. A computer program is stored in the memory. When the processor executes the computer program, the following steps are implemented:

[0122] In response to an API search request from an API requester, obtain the API search record of the API requester and the API interaction records between the API requester and each API developer;

[0123] Based on the API search record, the API interaction record, and the API requirement information in the API search request, select a recommended API from the tradable APIs in the API management platform;

[0124] Display the API description information of the recommended API to the API requester.

[0125] In an embodiment, when the processor executes the computer program, the following steps are further implemented:

[0126] Determine API requirement supplementary information based on the API search record and the API interaction record; use the API requirement supplementary information to supplement the API requirement information in the API search request to obtain API global requirement information; based on the API global requirement information, select a recommended API from the tradable APIs in the API management platform.

[0127] In an embodiment, when the processor executes the computer program, the following steps are further implemented:

[0128] Based on the API requester's selection operation of the recommended API according to the API description information of the recommended API, select a to-be-traded API from the recommended APIs; control the API requester and the API developer corresponding to the to-be-traded API to conduct an API transaction based on the to-be-traded API.

[0129] In an embodiment, when the processor executes the computer program, the following steps are further implemented:

[0130] In response to a monitoring request for a target API initiated by any API developer, when the API developer is the developer of the target API, obtain the usage record and usage evaluation information of the target API; send the usage record and usage evaluation information of the target API to the API developer; receive the updated version of the target API from the API developer and store the updated version of the target API; wherein, the updated version is obtained by the API developer upgrading the target API based on the usage record and usage evaluation information of the target API.

[0131] In an embodiment, when the processor executes the computer program, the following steps are further implemented:

[0132] In the case where any abnormality is detected in an API, a rollback request is sent to the API developer corresponding to the API; wherein, the rollback request includes the historical version information of the API; receive the rollback version information feedback by the API developer of the API based on the rollback request; perform a rollback on the API based on the rollback version information.

[0133] In one embodiment, when the processor executes the computer program, the following steps are further implemented:

[0134] Select a recommended API from the tradable APIs of the API management platform according to the API global requirement information and the API level of the API requester; wherein, the API level is determined based on the API certificate of the API requester and the API learning record.

[0135] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0136] In response to the API search request of the API requester, obtain the API search record of the API requester and the API interaction record between the API requester and each API developer;

[0137] Select a recommended API from the tradable APIs of the API management platform according to the API search record, the API interaction record, and the API requirement information in the API search request;

[0138] Display the API description information of the recommended API to the API requester.

[0139] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented:

[0140] Determine the API requirement supplementary information according to the API search record and the API interaction record; use the API requirement supplementary information to supplement the API requirement information in the API search request to obtain the API global requirement information; select a recommended API from the tradable APIs of the API management platform according to the API global requirement information.

[0141] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented:

[0142] Select a to-be-traded API from the recommended APIs according to the selection operation of the API requester on the API description information of the recommended API; control the API requester and the API developer corresponding to the to-be-traded API to perform an API transaction based on the to-be-traded API.

[0143] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented:

[0144] In response to a monitoring request for a target API initiated by any API developer, when the API developer is the developer of the target API, obtain the usage record and usage evaluation information of the target API; send the usage record and usage evaluation information of the target API to the API developer; receive the updated version of the target API from the API developer and store the updated version of the target API; wherein, the updated version is obtained by the API developer upgrading the target API based on the usage record and usage evaluation information of the target API.

[0145] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0146] When it is detected that any API is abnormal, send a rollback request to the API developer corresponding to the API; wherein, the rollback request includes the historical version information of the API; receive the rollback version information feedback by the API developer of the API based on the rollback request; and roll back the API based on the rollback version information.

[0147] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0148] Select a recommended API from the tradable APIs in the API management platform according to the API global requirement information and the API level of the API requester; wherein, the API level is determined based on the API certificate and API learning record of the API requester.

[0149] In one embodiment, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, the following steps are implemented:

[0150] In response to an API search request of an API requester, obtain the API search record of the API requester and the API interaction record between the API requester and each API developer;

[0151] Select a recommended API from the tradable APIs in the API management platform according to the API search record, API interaction record, and API requirement information in the API search request;

[0152] Display the API description information of the recommended API to the API requester.

[0153] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0154] Determine the API requirement supplementary information according to the API search record and the API interaction record; use the API requirement supplementary information to supplement the API requirement information in the API search request to obtain the API global requirement information; select the recommended API from the tradable APIs in the API management platform according to the API global requirement information.

[0155] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented:

[0156] Select the API to be traded from the recommended APIs according to the API description information of the recommended APIs and the selection operation of the API requester for the recommended APIs; control the API requester and the API developer corresponding to the API to be traded to conduct API trading based on the API to be traded.

[0157] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented:

[0158] In response to a monitoring request for a target API initiated by any API developer, when the API developer is the developer of the target API, obtain the usage record and usage evaluation information of the target API; send the usage record and usage evaluation information of the target API to the API developer; receive the updated version of the target API from the API developer and store the updated version of the target API; wherein, the updated version is obtained by the API developer upgrading the target API based on the usage record and usage evaluation information of the target API.

[0159] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented:

[0160] In the case of detecting that any API is abnormal, send a rollback request to the API developer corresponding to the API; wherein, the rollback request includes the historical version information of the API; receive the rollback version information fed back by the API developer of the API based on the rollback request; roll back the API based on the rollback version information.

[0161] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented:

[0162] Select the recommended API from the tradable APIs in the API management platform according to the API global requirement information and the API level of the API requester; wherein, the API level is determined based on the API certificate and API learning record of the API requester.

[0163] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in this application are all information and data that have been fully authorized by all parties, and the collection, use, and processing of relevant data need to comply with relevant regulations.

[0164] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above methods. Among them, any reference to a memory, database, or other medium used in the embodiments provided in this application can include at least one of non-volatile and volatile memories. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc. The databases involved in the embodiments provided in this application can include at least one of relational databases and non-relational databases. Non-relational databases can include distributed databases based on blockchain, etc., without limitation. The processors involved in the embodiments provided in this application can be general-purpose processors, central processors, graphics processors, digital signal processors, programmable logic devices, data processing logics based on quantum computing, etc., without limitation.

[0165] The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity of description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered to be within the scope described in this specification.

[0166] The above-described embodiments merely represent several implementation manners of the present application. The description thereof is relatively specific and detailed, but it should not be construed as a limitation on the patent scope of the present application. It should be noted that for those of ordinary skill in the art, without departing from the concept of the present application, several modifications and improvements can still be made, and these all fall within the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the appended claims.

Claims

1. An API management method, characterized in that: Applied to an application programming interface (API) management platform, the method includes: In response to an API search request from an API demander, obtain the API search record of the API demander and the API interaction record between the API demander and each API developer; Selecting a recommended API from tradable APIs on the API management platform according to the API search record, the API interaction record, and the API requirement information in the API search request; The API description information of the recommended API is displayed to the API demander.

2. The method according to claim 1, characterized in that: The selecting a recommended API from the tradable APIs on the API management platform according to the API search record, the API interaction record, and the API requirement information in the API search request includes: Determine the API requirement supplementary information according to the API search record and the API interaction record; The API demand supplement information is used to supplement the API demand information in the API search request to obtain API global demand information; According to the API global demand information, a recommended API is selected from the tradable APIs on the API management platform.

3. The method according to claim 1, characterized in that After displaying the API description information of the recommended API to the API demander, the method further includes: According to the selection operation of the recommended API by the API demander based on the API description information of the recommended API, selecting an API to be traded from the recommended API; The API demander and the API developer corresponding to the API to be traded are controlled to conduct API transactions based on the API to be traded.

4. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: In response to a monitoring request for a target API initiated by any API developer, if the API developer is the developer of the target API, obtaining usage records and usage evaluation information of the target API; Sending the usage record and usage evaluation information of the target API to the API developer; Receive an updated version of the target API from the API developer, and store the updated version of the target API; wherein the updated version is obtained by the API developer by upgrading the target API based on the usage record and usage evaluation information of the target API.

5. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: When an abnormality is detected in any API, a rollback request is sent to the API developer corresponding to the API; wherein the rollback request includes the historical version information of the API; Receiving rollback version information fed back by the API developer of the API based on the rollback request; The API is rolled back based on the rollback version information.

6. The method according to claim 2, characterized in that The selecting a recommended API from the tradable APIs on the API management platform according to the API global demand information includes: According to the API global demand information and the API level of the API demander, a recommended API is selected from the tradable APIs of the API management platform; wherein the API level is determined based on the API certificate and API learning record of the API demander.

7. An API management device, characterized in that: The device comprises: An acquisition module, configured to respond to an API search request from an API demander, acquire the API search record of the API demander, and the API interaction record between the API demander and each API developer; A selection module, configured to select a recommended API from tradable APIs on the API management platform according to the API search record, the API interaction record, and the API requirement information in the API search request; The display module is used to display the API description information of the recommended API to the API demander.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images