CN109542644B

CN109542644B - Application programming interface calling method and device

Info

Publication number: CN109542644B
Application number: CN201811376629.0A
Authority: CN
Inventors: 康翔宇; 冷浩然; 张钦
Original assignee: Beijing Xiaomi Mobile Software Co Ltd
Current assignee: Beijing Xiaomi Mobile Software Co Ltd
Priority date: 2018-11-19
Filing date: 2018-11-19
Publication date: 2022-12-09
Anticipated expiration: 2038-11-19
Also published as: CN109542644A

Abstract

The disclosure relates to an application programming interface calling method and device. The method comprises the following steps: receiving a calling request sent by a calling terminal; calling a target API corresponding to the interface identifier according to a plurality of parameters required by calling the target API and included in the calling request, and acquiring a target operation result of the target API; according to the main channel identification and the auxiliary channel identification, inquiring a preset tree-shaped calling relation corresponding to the main channel identification, and acquiring target characteristic information recorded by an auxiliary channel corresponding to the auxiliary channel identification in the tree-shaped calling relation, wherein the tree-shaped calling relation comprises the main channel corresponding to the main channel identification, a plurality of auxiliary channels corresponding to the main channel and characteristic information recorded by each auxiliary channel; and sending calling feedback information to the calling terminal according to the target characteristic information and the target operation result. The technical scheme simplifies the process of acquiring the characteristic information by the calling terminal, improves the efficiency of calling the target API, and further reduces the coupling of the called server in the process of calling the API.

Description

Application programming interface calling method and device

Technical Field

The disclosure relates to the technical field of terminal control, and in particular relates to a method and a device for calling an application programming interface.

Background

With the rapid development of communication technology and mobile internet, smart terminals become indispensable articles for use in daily life of people, and in order to realize multiple functions of smart terminals, users usually install various APPs (applications) on smart terminals, such as shopping APPs, video APPs, or communication APPs. Assuming that a plurality of APPs are installed on the smart terminal, when a user uses a certain function of a first APP, the user may need support of a second APP, and at this time, the first APP may call an API (Application Programming Interface) provided by the second APP, and support the function provided by the first APP through a service processing capability provided by the API.

Disclosure of Invention

In order to overcome the problems in the related art, embodiments of the present disclosure provide a method and an apparatus for calling an application programming interface. The technical scheme is as follows:

according to a first aspect of the embodiments of the present disclosure, there is provided an application programming interface calling method, applied to a called server, including:

receiving a calling request sent by a calling terminal, wherein the calling request comprises a main channel identifier and an auxiliary channel identifier of the calling terminal, an interface identifier of a target API needing to be called, and a plurality of parameters required by calling the target API;

calling a target API corresponding to the interface identifier according to a plurality of parameters required for calling the target API and included in the calling request, and acquiring a target operation result of the target API;

querying a preset tree-shaped calling relationship corresponding to the main channel identifier according to the main channel identifier and the auxiliary channel identifiers, and acquiring target characteristic information recorded by the auxiliary channels corresponding to the auxiliary channel identifiers in the tree-shaped calling relationship, wherein the tree-shaped calling relationship comprises the main channel corresponding to the main channel identifier, a plurality of auxiliary channels corresponding to the main channel, and characteristic information recorded by each auxiliary channel;

and sending calling feedback information to the calling terminal according to the target characteristic information and the target operation result so that the calling terminal can display the calling result according to the calling feedback information.

The technical scheme provided by the embodiment of the disclosure can have the following beneficial effects: the called server can record the characteristic information corresponding to different auxiliary channels by presetting a tree-shaped calling relation aiming at the target API, and after receiving a calling request of the calling terminal, the called server can inquire the tree-shaped calling relation according to the main channel identifier and the auxiliary channel identifier included in the calling request to acquire the characteristic information corresponding to the current auxiliary channel of the calling terminal, so that the process of acquiring the characteristic information by the calling terminal is simplified, the efficiency of calling the target API is improved, and the coupling of the called server in the process of calling the API is reduced.

In an embodiment, the calling the target API corresponding to the interface identifier according to a plurality of parameters included in the call request and required for calling the target API, and obtaining the target operation result of the target API includes:

performing interface authentication on the calling request according to the main channel identifier and the auxiliary channel identifier;

if the interface authentication indicates that the calling terminal has the authority to call the target API, calling the target API corresponding to the interface identification according to a plurality of parameters required for calling the target API and included in the calling request, and acquiring a target operation result of the target API.

In an embodiment, the calling the target API corresponding to the interface identifier according to a plurality of parameters, included in the call request, required for calling the target API, and obtaining the target operation result of the target API includes:

determining whether the calling request comprises a preset parameter, wherein the preset parameter is a legal parameter necessary for calling the target API;

if the calling request comprises the preset parameters, calling a target API corresponding to the interface identifier according to a plurality of parameters which are included in the calling request and are required for calling the target API, and acquiring a target operation result of the target API.

In one embodiment, the invocation request further includes a primary channel token and a secondary channel key; the calling the target API corresponding to the interface identifier according to the plurality of parameters, included in the calling request, required for calling the target API, and the obtaining of the target operation result of the target API comprises the following steps:

according to the main channel token and the auxiliary channel key included in the calling request, carrying out request token verification on the calling request;

if the request token verification indicates that the calling request is a legal request, calling a target API corresponding to the interface identifier according to a plurality of parameters required for calling the target API and included in the calling request, and acquiring a target operation result of the target API.

In one embodiment, the method further comprises:

receiving a synchronization instruction sent by an API management platform, wherein the synchronization instruction comprises the tree call relation;

and storing the tree-shaped calling relation according to the synchronous instruction.

According to a second aspect of the embodiments of the present disclosure, there is provided an application programming interface calling method, applied to a calling terminal, including:

sending a calling request to a called server, wherein the calling request comprises a main channel identifier and an auxiliary channel identifier of the calling terminal, an interface identifier of a target API to be called and a plurality of parameters required by calling the target API;

receiving calling feedback information sent by the called server, wherein the calling feedback information comprises a target operation result obtained by calling the target API and target characteristic information of an auxiliary channel record corresponding to the auxiliary channel identifier in a tree-shaped calling relation preset by the called server, and the tree-shaped calling relation comprises a main channel corresponding to the main channel identifier, a plurality of auxiliary channels corresponding to the main channel and characteristic information of each auxiliary channel record;

and displaying a calling result according to the target operation result and the target characteristic information.

The technical scheme provided by the embodiment of the disclosure can have the following beneficial effects: the calling terminal can carry the main channel identifier and the auxiliary channel identifier in the calling request, so that the called server can conveniently obtain the characteristic information corresponding to the current auxiliary channel of the calling terminal according to the main channel identifier and the auxiliary channel identifier query tree-shaped calling relation, the scheme of obtaining the characteristic information while calling the target API is realized, the process of obtaining the characteristic information by the calling terminal is simplified, the efficiency of calling the target API is improved, and the coupling of the called server in the process of calling the API is further reduced.

According to a third aspect of the embodiments of the present disclosure, there is provided an application programming interface calling method, applied to a development terminal, including:

acquiring a first registration instruction, and sending first registration information to an API (application programming interface) management platform in response to the first registration instruction, wherein the first registration information comprises an application name of a calling application and an interface identifier of a target API which the calling application needs to call, so that the API management platform creates a main channel aiming at the target API, the main channel identifier of the main channel is the same as the application name, and the development terminal is a terminal for developing the calling application;

receiving and displaying first feedback information sent by the API management platform, wherein the first feedback information comprises the main channel identification;

obtain the second registration instruction, respond to the second registration instruction sends second registration information to API management platform, second registration information include with a plurality of subsidiary channel identifications that main channel identification corresponds to and the characteristic information that every subsidiary channel identification corresponds, so that API management platform basis a plurality of subsidiary channel identifications, and the characteristic information that every subsidiary channel identification corresponds create under the main channel respectively with a plurality of subsidiary channels that a plurality of subsidiary channel identifications correspond, every subsidiary channel record has the characteristic information rather than corresponding, forms the tree-shaped calling relation.

The technical scheme provided by the embodiment of the disclosure can have the following beneficial effects: the development terminal can send the first registration information and the second registration information to the API management platform according to the instruction of a developer calling the application, so that the API management platform can form a tree-shaped calling relationship according to the content included by the first registration information and the second registration information, and after the API management platform synchronously stores the tree-shaped calling relationship in the called server, the calling terminal can call the target API and simultaneously obtain the characteristic information, the process of obtaining the characteristic information by the calling terminal is simplified, the efficiency of calling the target API is improved, and the coupling of the called server in the process of calling the API is further reduced.

According to a fourth aspect of the embodiments of the present disclosure, there is provided an application programming interface calling method, applied to an API management platform, including:

receiving first registration information sent by a development terminal, wherein the first registration information comprises an application name of a calling application and an interface identifier of a target API (application program interface) which needs to be called by the calling application, and the development terminal is a terminal for developing the calling application;

according to the application name included in the first registration information, a main channel of the target API is established, and the main channel identification of the main channel is the same as the application name;

sending first feedback information to the development terminal, wherein the first feedback information comprises the main channel identification, so that the development terminal can conveniently acquire a plurality of auxiliary channel identifications corresponding to the main channel identification and characteristic information corresponding to each auxiliary channel identification;

receiving second registration information sent by the development terminal, wherein the second registration information comprises a plurality of auxiliary channel identifications corresponding to the main channel identifications and characteristic information corresponding to each auxiliary channel identification;

according to the plurality of auxiliary channel identifications included in the second registration information and the characteristic information corresponding to each auxiliary channel identification, a plurality of auxiliary channels respectively corresponding to the plurality of auxiliary channel identifications are established under the main channel, and each auxiliary channel records the characteristic information corresponding to the auxiliary channel, so that a tree-shaped calling relationship is formed;

and sending a synchronization instruction to the called server according to the tree call relation so as to facilitate the called server to synchronously store the tree call relation.

The technical scheme provided by the embodiment of the disclosure can have the following beneficial effects: the API management platform forms a tree-shaped calling relationship according to the contents included by the first registration information and the second registration information, and synchronizes the tree-shaped calling relationship to the called server, so that the calling terminal can acquire the characteristic information while calling the target API, the process of acquiring the characteristic information by the calling terminal is simplified, the efficiency of calling the target API is improved, and the coupling of the called server in the process of calling the API is reduced.

In one embodiment, the creating a main channel of the target API according to the application name included in the first registration information includes:

determining whether the first registration information passes an audit;

and if the first registration information passes the examination, creating a main channel of the target API according to the application name included in the first registration information.

In an embodiment, the creating, according to the multiple secondary channel identifiers and the feature information corresponding to each secondary channel identifier included in the second registration information, multiple secondary channels respectively corresponding to the multiple secondary channel identifiers in the primary channel, where each secondary channel records feature information corresponding to the secondary channel identifier, and forming a tree-shaped invocation relationship includes:

determining whether the second registration information passes an audit;

and if the second registration information passes the audit, according to a plurality of auxiliary channel identifications included in the second registration information and the characteristic information corresponding to each auxiliary channel identification, creating a plurality of auxiliary channels respectively corresponding to the plurality of auxiliary channel identifications under the main channel, wherein each auxiliary channel records the characteristic information corresponding to each auxiliary channel, and forming a tree-shaped calling relationship.

In one embodiment, the method further comprises:

distributing a primary channel token aiming at the target API for the primary channel;

assigning an auxiliary channel key to each of the plurality of auxiliary channels;

the sending a synchronization instruction to the called server according to the tree call relationship so that the called server synchronously stores the tree call relationship comprises:

and sending a synchronous instruction to the called server according to the tree-shaped calling relationship, the main channel token and the auxiliary channel key of each auxiliary channel, so that the called server synchronously stores the tree-shaped calling relationship, the main channel token and the auxiliary channel key of each auxiliary channel.

According to a fifth aspect of the embodiments of the present disclosure, there is provided an api calling apparatus, including:

the system comprises a first receiving module, a second receiving module and a calling module, wherein the first receiving module is used for receiving a calling request sent by a calling terminal, and the calling request comprises a main channel identifier and an auxiliary channel identifier of the calling terminal, an interface identifier of a target API needing to be called and a plurality of parameters required by calling the target API;

the calling module is used for calling the target API corresponding to the interface identifier according to a plurality of parameters which are included in the calling request and are required for calling the target API, and acquiring a target operation result of the target API;

the query module is used for querying a preset tree-shaped calling relationship corresponding to the main channel identifier according to the main channel identifier and the auxiliary channel identifiers, and acquiring target characteristic information recorded by the auxiliary channel corresponding to the auxiliary channel identifier in the tree-shaped calling relationship, wherein the tree-shaped calling relationship comprises the main channel corresponding to the main channel identifier, a plurality of auxiliary channels corresponding to the main channel and characteristic information recorded by each auxiliary channel;

and the first sending module is used for sending calling feedback information to the calling terminal according to the target characteristic information and the target operation result so that the calling terminal can display the calling result according to the calling feedback information.

In one embodiment, the calling module comprises:

the authentication submodule is used for carrying out interface authentication on the calling request according to the main channel identification and the auxiliary channel identification;

and the first calling submodule is used for calling the target API corresponding to the interface identifier according to a plurality of parameters required by calling the target API and included in the calling request if the interface authentication indicates that the calling terminal has the authority to call the target API, and acquiring a target operation result of the target API.

In one embodiment, the calling module comprises:

a determining submodule, configured to determine whether the call request includes a preset parameter, where the preset parameter is a legal parameter necessary for calling the target API;

and the second calling submodule is used for calling the target API corresponding to the interface identifier according to a plurality of parameters which are included in the calling request and are required for calling the target API if the calling request includes the preset parameters, and acquiring a target operation result of the target API.

In one embodiment, the calling module comprises:

the verification submodule is used for performing request token verification on the calling request according to the main channel token and the auxiliary channel key included in the calling request;

and the third calling submodule is used for calling the target API corresponding to the interface identifier according to a plurality of parameters required for calling the target API and included in the calling request if the request token verification indicates that the calling request is a legal request, and acquiring a target operation result of the target API.

In one embodiment, the apparatus further comprises:

the second receiving module is used for receiving a synchronization instruction sent by the API management platform, wherein the synchronization instruction comprises the tree-shaped calling relationship;

and the synchronization module is used for storing the tree-shaped calling relation according to the synchronization instruction.

According to a sixth aspect of the embodiments of the present disclosure, there is provided an application programming interface calling apparatus, including:

the second sending module is used for sending a calling request to a called server, wherein the calling request comprises a main channel identifier, an auxiliary channel identifier, an interface identifier of a target API to be called and a plurality of parameters required by calling the target API;

a third receiving module, configured to receive call feedback information sent by the called server, where the call feedback information includes a target operation result obtained by calling the target API and target feature information of an auxiliary channel record corresponding to the auxiliary channel identifier in a tree-shaped call relationship preset by the called server, where the tree-shaped call relationship includes a main channel corresponding to the main channel identifier, multiple auxiliary channels corresponding to the main channel, and feature information of each auxiliary channel record;

and the display module is used for displaying the calling result according to the target operation result and the target characteristic information.

According to a seventh aspect of the embodiments of the present disclosure, there is provided an api calling apparatus, including:

the system comprises a first acquisition module, a first registration module and a development terminal, wherein the first acquisition module is used for acquiring a first registration instruction and sending first registration information to an API (application programming interface) management platform in response to the first registration instruction, the first registration information comprises an application name of a calling application and an interface identifier of a target API which the calling application needs to call, so that the API management platform can create a main channel aiming at the target API, the main channel identifier of the main channel is the same as the application name, and the development terminal is a terminal for developing the calling application;

the fourth receiving module is used for receiving and displaying first feedback information sent by the API management platform, wherein the first feedback information comprises the main channel identifier;

and the second acquisition module is used for acquiring a second registration instruction, responding to the second registration instruction and sending second registration information to the API management platform, wherein the second registration information comprises a plurality of auxiliary channel identifications corresponding to the main channel identifications and characteristic information corresponding to each auxiliary channel identification, so that the API management platform can establish a plurality of auxiliary channels corresponding to the auxiliary channel identifications and characteristic information corresponding to each auxiliary channel identification under the main channel, and each auxiliary channel is recorded with the corresponding characteristic information to form a tree-shaped calling relation.

According to an eighth aspect of the embodiments of the present disclosure, there is provided an application programming interface calling apparatus, including:

a fifth receiving module, configured to receive first registration information sent by a development terminal, where the first registration information includes an application name of a calling application and an interface identifier of a target API that the calling application needs to call, and the development terminal is a terminal for developing the calling application;

a first creating module, configured to create a main channel of the target API according to an application name included in the first registration information, where a main channel identifier of the main channel is the same as the application name;

the third sending module is configured to send first feedback information to the development terminal, where the first feedback information includes the main channel identifier, so that the development terminal can obtain multiple auxiliary channel identifiers corresponding to the main channel identifier and feature information corresponding to each auxiliary channel identifier;

a sixth receiving module, configured to receive second registration information sent by the development terminal, where the second registration information includes multiple auxiliary channel identifiers corresponding to the main channel identifier and feature information corresponding to each auxiliary channel identifier;

the second creating module is used for creating a plurality of auxiliary channels respectively corresponding to the plurality of auxiliary channel identifications under the main channel according to the plurality of auxiliary channel identifications included in the second registration information and the characteristic information corresponding to each auxiliary channel identification, and each auxiliary channel records the characteristic information corresponding to each auxiliary channel, so that a tree-shaped calling relationship is formed;

and the fourth sending module is used for sending a synchronization instruction to the called server according to the tree call relation so as to facilitate the called server to synchronously store the tree call relation.

In one embodiment, the first creation module comprises:

the first determining submodule is used for determining whether the first registration information passes the audit;

and the first creating submodule is used for creating a main channel of the target API according to the application name included in the first registration information if the first registration information passes the audit.

In one embodiment, the second creation module comprises:

a second determining sub-module, configured to determine whether the second registration information passes the audit;

and the second creating submodule is used for creating a plurality of auxiliary channels respectively corresponding to the auxiliary channel identifications under the main channel according to the plurality of auxiliary channel identifications included in the second registration information and the characteristic information corresponding to each auxiliary channel identification if the second registration information passes the audit, and each auxiliary channel is recorded with the corresponding characteristic information to form a tree-shaped calling relationship.

In one embodiment, the apparatus further comprises:

a first distribution module for distributing a main channel token aiming at the target API for the main channel;

a second allocating module for allocating a secondary channel key for each of the plurality of secondary channels;

the fourth sending module includes:

and the sending submodule is used for sending a synchronous instruction to the called server according to the tree-shaped calling relationship, the main channel token and each auxiliary channel key of the auxiliary channel, so that the called server synchronously stores the tree-shaped calling relationship, the main channel token and each auxiliary channel key of the auxiliary channel.

According to a ninth aspect of the embodiments of the present disclosure, there is provided an application programming interface calling apparatus, including:

a first processor;

a first memory for storing first processor-executable instructions;

wherein the first processor is configured to:

receiving a calling request sent by a calling terminal, wherein the calling request comprises a main channel identifier and an auxiliary channel identifier of the calling terminal, an interface identifier of a target API to be called and a plurality of parameters required by calling the target API;

according to the main channel identification and the auxiliary channel identification, inquiring a preset tree-shaped calling relation corresponding to the main channel identification, and acquiring target characteristic information recorded by an auxiliary channel corresponding to the auxiliary channel identification in the tree-shaped calling relation, wherein the tree-shaped calling relation comprises the main channel corresponding to the main channel identification, a plurality of auxiliary channels corresponding to the main channel and characteristic information recorded by each auxiliary channel;

According to a tenth aspect of the embodiments of the present disclosure, there is provided an application programming interface calling apparatus, including:

a second processor;

a second memory for storing second processor-executable instructions;

wherein the second processor is configured to:

receiving calling feedback information sent by the called server, wherein the calling feedback information comprises a target operation result obtained by calling the target API and target characteristic information of an auxiliary channel record corresponding to the auxiliary channel identifier in a tree-shaped calling relationship preset by the called server, and the tree-shaped calling relationship comprises a main channel corresponding to the main channel identifier, a plurality of auxiliary channels corresponding to the main channel and characteristic information of each auxiliary channel record;

According to an eleventh aspect of the embodiments of the present disclosure, there is provided an application programming interface calling apparatus including:

a third processor;

a third memory for storing third processor-executable instructions;

wherein the third processor is configured to:

According to a twelfth aspect of the embodiments of the present disclosure, there is provided an application programming interface calling apparatus, including:

a fourth processor;

a fourth memory to store fourth processor-executable instructions;

wherein the fourth processor is configured to:

and sending a synchronization instruction to the called server according to the tree call relation so that the called server synchronously stores the tree call relation.

According to a thirteenth aspect of embodiments of the present disclosure, there is provided a computer-readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the steps of the method according to any one of the embodiments of the first aspect.

According to a fourteenth aspect of embodiments of the present disclosure, there is provided a computer-readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the steps of the method according to any one of the embodiments of the second aspect.

According to a fifteenth aspect of embodiments of the present disclosure, there is provided a computer-readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the steps of the method of any of the embodiments of the second aspect.

According to a sixteenth aspect of embodiments of the present disclosure, there is provided a computer-readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the steps of the method according to any one of the embodiments of the second aspect.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure.

FIG. 1 is a flow diagram illustrating an application programming interface call method in accordance with an illustrative embodiment.

FIG. 2 is a flowchart illustrating an application programming interface call method in accordance with an illustrative embodiment.

FIG. 3 is a flowchart illustrating an application programming interface call method in accordance with an illustrative embodiment.

FIG. 4 is a flowchart illustrating an application programming interface call method in accordance with an illustrative embodiment.

FIG. 5 is an interaction diagram illustrating an application programming interface call method in accordance with an illustrative embodiment.

Fig. 6a is a schematic diagram illustrating a structure of an api calling apparatus according to an exemplary embodiment.

FIG. 6b is a block diagram illustrating an API call apparatus in accordance with an exemplary embodiment.

Fig. 6c is a schematic diagram illustrating a structure of an api calling apparatus according to an exemplary embodiment.

Fig. 6d is a schematic diagram illustrating a structure of an api calling apparatus according to an exemplary embodiment.

Fig. 6e is a schematic diagram illustrating the structure of the api calling apparatus according to an exemplary embodiment.

Fig. 7 is a schematic diagram illustrating a structure of an api calling apparatus according to an exemplary embodiment.

Fig. 8 is a schematic diagram illustrating a structure of an api call apparatus according to an exemplary embodiment.

Fig. 9a is a schematic diagram illustrating a structure of an api calling apparatus according to an exemplary embodiment.

FIG. 9b is a block diagram illustrating an API call apparatus in accordance with an exemplary embodiment.

Fig. 9c is a schematic diagram illustrating a structure of an api calling apparatus according to an exemplary embodiment.

Fig. 9d is a schematic diagram illustrating a structure of an api calling apparatus according to an exemplary embodiment.

Fig. 10 is a block diagram illustrating a configuration of an api calling apparatus according to an exemplary embodiment.

Fig. 11 is a block diagram illustrating a configuration of an api calling apparatus according to an exemplary embodiment.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.

The technical scheme provided by the embodiment of the disclosure relates to a development terminal, an API (application programming interface) management platform, a called server and a calling terminal, wherein the development terminal is a terminal used by a developer calling an application when developing the calling application, such as a notebook computer, a tablet computer or a desktop computer; the API management platform is a platform which is set by the called server and is used for managing a plurality of APIs supported by the called server; the called server is a server capable of supporting the calling of the plurality of APIs; and the calling terminal installs a terminal using the calling application after the calling application is developed, such as a mobile phone, a tablet computer or a smart watch. In a scenario where the calling terminal calls the target API supported by the calling server, not only the calling result of the target API but also feature information related to the target API may be required, for example, in a scenario where the calling terminal calls the payment API, the calling terminal needs to obtain information such as the current postage, address, contact, and the like in addition to the calling result of the payment API in order to complete payment. In the related art, in order to obtain the information of the postage, the address, the contact person and the like, the calling terminal needs to add a parameter for calling the postage, a parameter for calling the address and a parameter for calling the contact person information in a calling request for calling the payment API, and the called server can add the postage, the address and the contact person obtained by calling in calling feedback information of the payment API and send the postage, the address and the contact person to the calling terminal. Or the calling terminal needs to send a request for calling the postage, a request for calling the address and a request for calling the contact information to the called server independently, and the calling server can respectively return the postage, the address and the contact to the calling terminal according to the received calling request. Therefore, the process of acquiring the characteristic information related to the payment API by the calling terminal is complicated, and the calling efficiency is low. In the technical scheme provided by the embodiment of the disclosure, the API management platform may form a tree-shaped call relationship according to information included in the first registration information and the second registration information sent by the development terminal, and synchronize the tree-shaped call relationship to the called server, where the tree-shaped call relationship includes a main channel for the payment API, a plurality of auxiliary channels corresponding to the main channel, and feature information recorded by each auxiliary channel. After receiving a calling request of a calling terminal, the called server can query the tree-shaped calling relationship according to the main channel identifier and the auxiliary channel identifier included in the calling request to acquire the characteristic information corresponding to the current auxiliary channel of the calling terminal, so that the process of acquiring the characteristic information by the calling terminal is simplified, the efficiency of calling a target API is improved, and the coupling of the called server in the process of calling the API is further reduced.

The embodiment of the disclosure provides an application programming interface calling method, and an execution main body for implementing the method comprises a development terminal, an API management platform, a calling terminal and a called server. According to the different implementation main bodies of the method, four sets of embodiments for realizing the application programming interface calling method are arranged in the embodiment of the disclosure, as follows:

development terminal side

Fig. 1 is a flowchart illustrating an application programming interface calling method applied to a development terminal according to an exemplary embodiment, where the application programming interface calling method, as shown in fig. 1, includes the following steps 101 and 103:

in step 101, a first registration instruction is obtained, and first registration information is sent to an API management platform in response to the first registration instruction, where the first registration information includes an application name of a calling application and an interface identifier of a target API that the calling application needs to call, so that the API management platform creates a main channel for the target API, the main channel identifier of the main channel is the same as the application name, and the development terminal is a terminal for developing the calling application.

By way of example, the called server supports the calling of a plurality of APIs, and for management, the called server is provided with an API management platform. The called server may publish the supported APIs to the API management platform as directed by an administrator of the API management platform.

When a developer develops the calling terminal, the use and the supported functions of the calling terminal can be planned, and the API required to be called by the calling application can be determined after the planning. The following target APIs are all payment APIs, and first, a developer may instruct a development terminal to log in an API management platform set by a called server, and after logging in, the development terminal may display a plurality of APIs published on the API management platform. The developer may consult the plurality of APIs and click on a payment API in the plurality of APIs. And after detecting the click, the development terminal displays a main channel creating page of the payment API, wherein an application name input box and a confirmation button are displayed in the main channel creating page. The developer may enter the name of the calling application in the application name input box and click a confirmation button. When detecting that the confirmation button is clicked, the development terminal confirms to obtain a first registration instruction, and at this time, the development terminal can send first registration information to the API management platform, where the first registration information includes an application name input by a developer in the application name input box and an interface identifier of the payment API.

For example, after receiving the first registration information, the API management platform may display a first audit page according to an instruction of an administrator of the API management platform, where the first audit page displays an application name and an interface identifier included in the first registration information, and also displays an audit pass button and an audit fail button. The administrator can review the first review page and review the first registration information. If the API management platform detects that the audit pass button is clicked, first audit information is determined to be obtained, and the first audit information indicates that the first registration information passes the audit; and if the API management platform detects that the audit fails to pass the button, determining to acquire first audit information, wherein the first audit information indicates that the first registration information fails to pass the audit.

If the API management platform determines that the first registration information passes the audit, a main channel of the payment API corresponding to the interface identifier can be created according to the application name and the interface identifier included in the first registration information, the main channel identifier is the application name of the calling application, then first feedback information is generated according to the main channel identifier, and the first feedback information is sent to the development terminal. In practical application, after the API management platform creates a main channel for the payment API corresponding to the interface identifier, the API management platform may also allocate a main channel token for the main channel, and generate first feedback information according to the main channel identifier and the main channel token and send the first feedback information to the development terminal. If the API management platform determines that the first registration information is not approved, the API management platform can send an approval failure prompt message to the development terminal. The development terminal can display the information after receiving the prompt that the audit fails, so that the development personnel can consult with the administrator of the API management platform in time after consulting.

In step 102, first feedback information sent by the API management platform is received and presented, where the first feedback information includes the primary channel identifier.

For example, after receiving the first feedback information sent by the API management platform, the development terminal may display information included in the first feedback information, so that the developer may determine in time whether the first registration information is approved. Specifically, the first feedback information comprises a main channel identifier and a main channel token, the development terminal displays a first feedback page, the main channel identifier of the main channel created by the API management platform and the main channel token distributed for the main channel are displayed on the first feedback page, and a developer can determine that the first registration information passes the audit after looking up the first feedback page and record the main channel identifier and the main channel token for developing the calling application.

In step 103, a second registration instruction is obtained, and second registration information is sent to the API management platform in response to the second registration instruction, where the second registration information includes a plurality of secondary channel identifiers corresponding to the primary channel identifier and feature information corresponding to each secondary channel identifier, so that the API management platform creates, according to the plurality of secondary channel identifiers and the feature information corresponding to each secondary channel identifier, a plurality of secondary channels respectively corresponding to the plurality of secondary channel identifiers in the primary channel, and each secondary channel records the feature information corresponding thereto, thereby forming a tree-shaped call relationship.

For example, after determining that the first registration information is approved, the developer may instruct the development terminal to display a sub-channel creation page, where the sub-channel creation page displays a plurality of sub-channel identification input boxes, a feature information input box corresponding to each sub-channel identification input box, and a confirmation button. Then, the developer can input the auxiliary channel identification in the auxiliary channel identification input boxes according to the requirement, and input the corresponding characteristic information in the characteristic information input box corresponding to each auxiliary channel identification input box.

Specifically, when planning the calling application, the developer may determine a terminal to which the calling application is applicable, for example, the calling application may be applicable to a mobile phone, a tablet computer, and a personal computer, that is, the calling application includes a mobile phone side application, a tablet computer side application, and a personal computer side application. Supposing that in order to improve the coverage rate of the mobile phone and the tablet personal computer calling the application, a developer determines that when a user calls a payment API by using a mobile phone end application, the postage is 0 yuan; when a user calls a payment API by using a tablet computer end application, the postage is 1 yuan; when a user calls the payment API by using the personal computer end application, the postage is 20 yuan, and a developer can set a plurality of auxiliary channels for the main channel corresponding to the calling application according to different applications. At this time, a developer can input a mobile phone application identifier corresponding to a mobile phone end application in a first auxiliary channel identifier input box of an auxiliary channel creation page, and input first postage information in a characteristic information input box corresponding to the first auxiliary channel identifier input box, wherein the first postage information indicates that postage is 0 yuan; inputting a tablet computer application identifier corresponding to a tablet computer end application in a second auxiliary channel identifier input box of the auxiliary channel creation page, and inputting second postage information in a characteristic information input box corresponding to the second auxiliary channel identifier input box, wherein the second postage information indicates that postage is 1 yuan; inputting a personal computer application identifier corresponding to a personal computer end application in a third auxiliary channel identifier input box of the auxiliary channel creation page, inputting third postage information in a characteristic information input box corresponding to the third auxiliary channel identifier input box, wherein the third postage information indicates that the postage is 20 yuan, and clicking a confirmation button after the input is finished.

And the development terminal confirms that a second registration instruction is obtained when the confirmation button is clicked, and at the moment, the development terminal can generate second registration information according to information input by the developer on the auxiliary channel creation page, wherein the second registration information comprises a plurality of auxiliary channel identifications corresponding to the main channel identification and characteristic information corresponding to each auxiliary channel identification. According to the above example, the second registration information may include an application identifier of the mobile phone application, and the first postage information corresponding to the application identifier of the mobile phone application; the application identifier of the tablet personal computer end application and the second postage information corresponding to the application identifier of the tablet personal computer end application; and the application identifier of the personal computer end application and the third postage information corresponding to the application identifier of the personal computer end application.

After receiving the second registration information, the API management platform may display a second audit page according to an instruction of an administrator of the API management platform, where the second audit page displays content included in the second registration information, and also displays an audit pass button and an audit fail button. The administrator can review the second review page and review the second registration information. If the API management platform detects that the audit pass button is clicked, second audit information is determined to be obtained, and the second audit information indicates that the second registration information passes the audit; and if the API management platform detects that the audit fails to pass the button, determining to acquire second audit information, wherein the second audit information indicates that the second registration information fails to pass the audit.

If the API management platform determines that the second registration information passes the audit, the first postage information corresponding to the application identifier of the mobile phone application can be obtained according to the application identifier of the mobile phone application included in the second registration information; the application identifier of the tablet personal computer end application and the second postage information corresponding to the application identifier of the tablet personal computer end application; and creating a first subsidiary channel corresponding to the application identifier of the mobile phone end application, a second subsidiary channel corresponding to the application identifier of the tablet personal computer end application and a third subsidiary channel corresponding to the application identifier of the personal computer end application under the previously created main channel, wherein the first subsidiary channel is recorded with first postage information, the second subsidiary channel is recorded with second postage information, the third subsidiary channel is recorded with third postage information, and a tree-shaped calling relationship can be formed according to the information. After the API platform forms the tree-shaped calling relationship, an auxiliary channel key can be distributed for each auxiliary channel included in the tree-shaped calling relationship, and then second feedback information is sent to the development terminal according to the auxiliary channel key of each auxiliary channel. After receiving the second feedback information sent by the API management platform, the development terminal may display the auxiliary channel key of each auxiliary channel included in the second feedback information, so that the developer may determine that the second registration information is approved in time, and record the auxiliary channel key of each auxiliary channel for developing the calling application.

If the API management platform determines that the second registration information is not approved, a prompt message indicating that the second registration information is not approved may be sent to the development terminal. The development terminal can display the information after receiving the audit failure prompt information, so that a developer can consult with an administrator of the API management platform in time after consulting.

In the technical scheme provided by the embodiment of the disclosure, the development terminal can send the first registration information and the second registration information to the API management platform according to the instruction of the developer calling the application, so that the API management platform forms a tree-shaped calling relationship according to the content included in the first registration information and the second registration information, and after the API management platform synchronously stores the tree-shaped calling relationship in the called server, the calling terminal can obtain the feature information while calling the target API, thereby simplifying the process of obtaining the feature information by the calling terminal, improving the efficiency of calling the target API, and further reducing the coupling of the called server in the process of calling the API.

API management platform side

Fig. 2 is a flowchart illustrating an application programming interface calling method according to an exemplary embodiment, where the method is used for an API management platform, and the API management platform may be a stand-alone server or may be disposed in the called server, which is not limited in this disclosure. As shown in fig. 2, the api call method includes the following steps 201 to 206:

in step 201, first registration information sent by a development terminal is received, where the first registration information includes an application name of a calling application and an interface identifier of a target API that the calling application needs to call.

The development terminal is a terminal for developing the calling application.

For example, the development terminal may log in the API management platform and establish a network connection with the API management platform. When a developer develops the calling terminal, the use and the supported functions of the calling terminal can be planned, and the API required to be called by the calling application can be determined after the planning. The embodiment of the present disclosure is described by taking an example that the calling application needs to call the payment API supported by the called server, and the following target APIs are all payment APIs.

When the development terminal obtains a first registration instruction of a developer, first registration information may be sent to the API management platform, where the first registration information includes an application name of the calling application and an interface identifier of the payment API.

In step 202, a main channel of the target API is created according to the application name included in the first registration information, and the main channel identifier of the main channel is the same as the application name.

For example, after receiving the first registration information, the API management platform may first determine whether the first registration information passes the audit, and when the first registration information passes the audit, create a main channel for the payment API according to an application name included in the first registration information.

Specifically, the API management platform may display a first audit page according to an instruction of an administrator of the API management platform, where the first audit page displays an application name and an interface identifier included in the first registration information, and also displays an audit pass button and an audit fail button. The administrator can review the first review page and review the first registration information. If the API management platform detects that the audit-passing button is clicked, first audit information is determined to be obtained, and the first audit information indicates that the first registration information passes the audit; if the API management platform detects that the audit is not passed and the button is clicked, the first audit information is determined to be obtained, and the first audit information indicates that the first registration information is not passed and audited.

If the API management platform determines that the first registration information passes the audit, a main channel of the payment API corresponding to the interface identifier may be created according to the application name and the interface identifier included in the first registration information, where the main channel identifier is the application name of the calling application. In practical application, after the API management platform creates a main channel for the payment API corresponding to the interface identifier, a main channel token may be further allocated to the main channel.

If the API management platform determines that the first registration information is not approved, a prompt message indicating that the first registration information is not approved may be sent to the development terminal. The development terminal can display the information after receiving the prompt that the audit fails, so that the development personnel can consult with the administrator of the API management platform in time after consulting.

In step 203, first feedback information is sent to the development terminal, where the first feedback information includes the primary channel identifier, so that the development terminal can obtain multiple secondary channel identifiers corresponding to the primary channel identifier and feature information corresponding to each secondary channel identifier.

For example, after creating a main channel for a payment API corresponding to the interface identifier, the API management platform may send first feedback information to the development terminal according to the main channel identifier of the main channel. After the development terminal receives the first feedback information, the information included in the first feedback information can be displayed, so that a developer can timely determine that the first registration information passes the audit.

In practical application, after distributing the main channel token for the main channel, the API management platform may send first feedback information to the development terminal according to the main channel identifier of the main channel and the main channel token distributed for the main channel. After receiving the first feedback information, the development terminal may display information included in the first feedback information, so that a developer can determine that the first registration information passes the audit in time, and record the main channel identifier and the main channel token for developing the calling application.

In step 204, second registration information sent by the development terminal is received, where the second registration information includes a plurality of secondary channel identifiers corresponding to the primary channel identifier and feature information corresponding to each secondary channel identifier.

For example, after determining that the first registration information is approved, the developer may input a second registration instruction on the development terminal according to the previous plan, and the development terminal may send second registration information to the API management platform according to the second registration instruction, where the second registration information includes a plurality of auxiliary channel identifiers corresponding to the main channel identifiers and feature information corresponding to each auxiliary channel identifier.

Specifically, when planning the calling application, the developer may further determine a terminal to which the calling application is applicable, for example, the calling application may be applicable to a mobile phone, a tablet computer, and a personal computer, that is, the calling application includes a mobile phone side application, a tablet computer side application, and a personal computer side application. Supposing that in order to improve the coverage rate of the mobile phone and the tablet computer for calling the application, a developer determines that when a user calls a payment API by using a mobile phone end application, the postage is 0 yuan; when the user calls the payment API by using the application of the tablet computer terminal, the postage is 1 yuan; when a user calls a payment API by using a personal computer end application, the postage is 20 yuan, a developer can set a plurality of auxiliary channels for a main channel corresponding to the calling application according to different applications, namely a second registration instruction input by the developer can indicate that a plurality of auxiliary channel identifications corresponding to the main channel identification are an application identification of a mobile phone end application, an application identification of a tablet personal computer end application and an application identification of the personal computer end application respectively, feature information corresponding to the three auxiliary channel identifications respectively is first postage information with standard postage of 0 yuan, second postage information with standard postage of 1 yuan and third postage information with standard postage of 20 yuan. At this time, the development terminal may generate second registration information according to the content indicated by the second registration instruction, where the second registration information may include an application identifier of the mobile phone application and first postage information corresponding to the application identifier of the mobile phone application; the application identifier of the tablet computer end application and the second postage information corresponding to the application identifier of the tablet computer end application; and the application identifier of the personal computer end application and the third postage information corresponding to the application identifier of the personal computer end application.

In step 205, according to the multiple secondary channel identifiers included in the second registration information and the feature information corresponding to each secondary channel identifier, multiple secondary channels respectively corresponding to the multiple secondary channel identifiers are created in the primary channel, and each secondary channel records the feature information corresponding thereto, so as to form a tree-shaped invocation relationship.

For example, after receiving the second registration information, the API management platform may first determine whether the second registration information passes the audit, and when the second registration information passes the audit, create a plurality of auxiliary channels respectively corresponding to the plurality of auxiliary channel identifiers in the main channel according to the plurality of auxiliary channel identifiers included in the second registration information and the feature information corresponding to each auxiliary channel identifier, where each auxiliary channel records the feature information corresponding to the auxiliary channel identifier, so as to form a tree call relationship.

Specifically, the API management platform may display a second audit page according to an instruction of the administrator, where the second audit page displays content included in the second registration information, and also displays an audit pass button and an audit fail button. The administrator may review the second review page to review the second registration information. If the API management platform detects that the audit pass button is clicked, second audit information is determined to be obtained, and the second audit information indicates that the second registration information passes the audit; and if the API management platform detects that the audit fails to pass the button, determining to acquire second audit information, wherein the second audit information indicates that the second registration information fails to pass the audit.

If the API management platform determines that the second registration information passes the audit, first postage information corresponding to the application identifier of the mobile phone application can be obtained according to the application identifier of the mobile phone application included in the second registration information; the application identifier of the tablet computer end application and the second postage information corresponding to the application identifier of the tablet computer end application; and an application identifier of a personal computer end application, third postage information corresponding to the application identifier of the personal computer end application, a first auxiliary channel corresponding to the application identifier of the mobile phone end application, a second auxiliary channel corresponding to the application identifier of the tablet personal computer end application and a third auxiliary channel corresponding to the application identifier of the personal computer end application are created under a previously created main channel, the first auxiliary channel records first postage information, the second auxiliary channel records second postage information, the third auxiliary channel records third postage information, and a tree-shaped calling relationship can be formed according to the information. In practical application, after the API platform forms the tree-shaped calling relationship, it may also allocate an auxiliary channel key to each auxiliary channel included in the tree-shaped calling relationship, and send second feedback information to the development terminal, where the second feedback information includes the auxiliary channel key allocated by the API management platform to each auxiliary channel. After receiving the second feedback information sent by the API management platform, the development terminal may display the auxiliary channel key of each auxiliary channel included in the second feedback information, so that the developer may determine that the second registration information is approved in time, and record the auxiliary channel key of each auxiliary channel for developing the calling application.

In step 206, a synchronization instruction is sent to the called server according to the tree call relationship, so that the called server synchronously stores the tree call relationship.

For example, after obtaining the tree call relationship, the API management platform may synchronize the tree call relationship to a called server supporting the payment API call in time. Specifically, the API management platform is provided with a synchronous interface, and the synchronous interface displays the tree-shaped calling relation and the synchronous button acquired by the API management platform in a graph-text mode. The administrator may refer to the tree-call relationship again, determine whether there is a problem between the primary channel and the plurality of secondary channels included in the tree-call relationship, and click the synchronization button when it is determined that there is no error. When detecting that the synchronization button is clicked, the API management platform determines to acquire a synchronization instruction, and at this time, the API management platform may synchronize the tree-shaped calling relationship to a called server supporting the payment API call. If the API management platform is arranged in the called server, the API management platform can share the storage address of the tree-shaped calling relation to the called server at the moment; if the API management platform is an independent server, the API management platform may send the tree call relationship to the called server, so that the called server may store the tree call relationship.

In practical application, when the API management platform synchronizes the tree call relationship to the called server, the API management platform may also synchronize a primary channel token, which is distributed by the API management platform for the primary channel included in the tree call relationship and is specific to the payment API, and a secondary channel key, which is distributed for each secondary channel included in the tree call relationship, to the called server, so that the called server performs interface authentication on the call request when determining that the payment API is called.

In the technical scheme provided by the embodiment of the disclosure, the API management platform forms a tree-shaped calling relationship according to the contents included by the first registration information and the second registration information, and synchronizes the tree-shaped calling relationship to the called server, so that the calling terminal can acquire the feature information while calling the target API, the process of acquiring the feature information by the calling terminal is simplified, the efficiency of calling the target API is improved, and the coupling of the called server in the process of calling the API is reduced.

Calling terminal side

Fig. 3 is a flowchart illustrating an application programming interface calling method according to an exemplary embodiment, where the method is applied to a calling terminal, and the calling terminal may be a mobile phone, a tablet computer, or a personal computer, which is not limited in this disclosure. As shown in fig. 3, the api call method includes the following steps 301 to 303:

in step 301, a call request is sent to a called server, where the call request includes a primary channel identifier of the calling terminal, a secondary channel identifier, an interface identifier of a target API to be called, and a plurality of parameters required for calling the target API.

For example, the user may install and use the calling application on a mobile phone, a tablet computer, or a personal computer, and if the mobile phone, the tablet computer, or the personal computer determines that the calling application needs to call the target API according to the use of the user, the mobile phone, the tablet computer, or the personal computer may send a calling request to the called host server supporting the target API. The calling terminal is taken as a mobile phone, a target API is taken as a payment API for illustration, a user uses the calling application on the mobile phone, if the calling application needs to call the payment API in the using process, the calling terminal can obtain the application name of the calling application as a main channel identifier, the application identifier of the calling application at the mobile phone end is taken as an auxiliary channel identifier, and then a calling request is sent to a called server supporting calling of the payment API according to the main channel identifier, the auxiliary channel identifier, the interface identifier of the payment API and a plurality of parameters required for calling the payment API.

After receiving the call request, the called server may first transmit a plurality of parameters included in the call request and required for calling the payment API to the payment API, where the payment API may operate according to the plurality of parameters and output an operation result, where the operation result is a target operation result. And then querying a preset tree-shaped calling relationship corresponding to the main channel identifier, namely querying a tree-shaped calling relationship corresponding to the main channel identifier included in the calling request and a main channel in a plurality of preset tree-shaped calling relationships aiming at the payment API. Specifically, the called server may obtain a plurality of preset tree-shaped calling relations for the payment API, then obtain a main channel identifier of a main channel included in each tree-shaped calling relation in the plurality of tree-shaped calling relations, and further take the tree-shaped calling relation in which the main channel identifier is the main channel of the application name of the calling application as the tree-shaped calling relation corresponding to the main channel identifier included in the calling request, where three subsidiary channels are respectively located below the main channel of the tree-shaped calling relation, a first subsidiary channel corresponds to the application identifier of the mobile phone end application, and feature information recorded by the first subsidiary channel is first postage information; the second auxiliary channel corresponds to the application identifier applied by the tablet personal computer end, and the characteristic information recorded by the second auxiliary channel is second postage information; the third subsidiary channel corresponds to the application identifier of the personal computer side application, and the characteristic information recorded by the third subsidiary channel is third postage information. And then the called server can acquire the first postage information recorded by the first auxiliary channel as target characteristic information according to the application identifier of the mobile phone application included in the calling request, further generate calling feedback information according to the target characteristic information and a target operation result, and send the calling feedback information to the calling terminal.

In step 302, call feedback information sent by the called server is received, where the call feedback information includes a target operation result obtained by calling the target API and target feature information of an auxiliary channel record corresponding to the auxiliary channel identifier in a tree call relationship preset by the called server, and the tree call relationship includes a main channel corresponding to the main channel identifier, a plurality of auxiliary channels corresponding to the main channel, and feature information recorded by each auxiliary channel.

In step 303, a calling result is displayed according to the target operation result and the target feature information.

For example, the calling terminal may receive, through a network connection established with the called server, calling feedback information sent by the called server, where the calling feedback information includes the target feature information and the target operation result, and then display the calling result according to the target feature information and the target operation result. For example, the calling terminal may display a payment interface, where the payment interface displays a payment method indicated by the target operation result, and also displays a postage amount to be paid and indicated by the first postage information, where the postage amount is 0 yuan in the embodiment of the present disclosure.

According to the technical scheme, the calling terminal can carry the main channel identification and the auxiliary channel identification in the calling request, so that the called server can obtain the characteristic information corresponding to the current auxiliary channel of the calling terminal according to the main channel identification and the auxiliary channel identification query tree-shaped calling relation, the scheme that the target API is called and the characteristic information is obtained is achieved, the process that the calling terminal obtains the characteristic information is simplified, the efficiency of calling the target API is improved, and the coupling of the called server in the process of calling the API is reduced.

Called server side

Fig. 4 is a flowchart illustrating an application programming interface calling method for an application and a called server according to an exemplary embodiment, where the application programming interface calling method, as shown in fig. 4, includes the following steps 401 to 404:

in step 401, a call request sent by a calling terminal is received, where the call request includes a primary channel identifier, a secondary channel identifier, an interface identifier of a target API to be called, and a plurality of parameters required for calling the target API.

The calling terminal is taken as a mobile phone, a target API is taken as a payment API for illustration, a user uses the calling application on the mobile phone, if the calling application needs to call the payment API in the using process, the mobile phone can obtain the application name of the calling application as a main channel identifier, the application identifier of the calling application at the mobile phone end is taken as an auxiliary channel identifier, and then a calling request is sent to a called server supporting calling of the payment API according to the main channel identifier, the auxiliary channel identifier, the interface identifier of the payment API and a plurality of parameters required for calling the payment API.

In step 402, according to a plurality of parameters included in the call request and required for calling the target API, the target API corresponding to the interface identifier is called, and a target operation result of the target API is obtained.

For example, after receiving the call request, the called server may first transmit a plurality of parameters included in the call request and required for calling the payment API to the payment API, where the payment API may perform operation according to the plurality of parameters and output an operation result, where the operation result is a target operation result.

Optionally, after the called server receives the call request, the called server may first perform interface authentication on the call request according to the primary channel identifier and the secondary channel identifier included in the call request, that is, determine whether the calling terminal has an authority to call the payment API. In the actual application, the called server can determine whether an API management platform arranged by the called server audits first registration information and second registration information sent by the development terminal of the called application, and if the API management platform audits the first registration information and the second registration information sent by the development terminal of the called application, the calling terminal is determined to have the authority to call the payment API; and if the API management platform does not check the first registration information or the second registration information sent by the development terminal calling the application, confirming that the calling terminal does not have the authority to call the payment API. If the called server determines that the calling terminal has the authority to call the payment API, a plurality of parameters required by calling the payment API and included in the calling request can be transmitted to the payment API, the payment API can operate according to the parameters, and then the operation result output by the payment API is used as the target operation result. And if the called server determines that the calling terminal does not have the authority to call the payment API, returning feedback information indicating call failure to the calling terminal.

Or, after receiving the call request or performing interface authentication on the call request, the called server may determine whether the call request includes a preset parameter, where the preset parameter is a legal parameter necessary for calling the payment API, that is, determine whether the preset parameter is included in a plurality of parameters included in the call request for calling the payment API. If the call request includes the preset parameters, the called server may transmit a plurality of parameters, which are included in the call request and are required for calling the payment API, to the payment API, and the payment API may operate according to the plurality of parameters, and then take an operation result output by the payment API as a target operation result. If the called server determines that the calling request does not comprise the preset parameters, feedback information indicating calling failure is returned to the calling terminal.

For example, after the API management platform obtains the tree call relationship, a synchronization instruction may be sent to the called server, where the synchronization instruction includes the tree call relationship, and may further include a primary channel token allocated by the API platform for the primary channel included in the tree call relationship and a secondary channel key allocated for each secondary channel included in the tree call relationship. The called server can synchronously store the information included in the synchronization instruction according to the synchronization instruction.

If the calling application needs to call the payment API in the process of using the calling application, the calling terminal can obtain the application name of the calling application as a main channel identifier, the application identifier of the calling application is used as an auxiliary channel identifier by the mobile phone terminal, and then a calling request is sent to a called server supporting calling of the payment API according to the main channel identifier, a pre-stored main channel token, the auxiliary channel identifier, a pre-stored auxiliary channel key, an interface identifier of the payment API and a plurality of parameters required for calling the payment API. After the called server receives the calling request, or performs interface authentication on the calling request, or after the calling request is determined to include preset parameters, request token verification can be performed on the calling request according to the main channel token and the auxiliary channel key included in the calling request, that is, whether the main channel token and the auxiliary channel key included in the calling request are matched with the main channel token corresponding to the main channel identifier and the auxiliary channel key corresponding to the auxiliary channel identifier, which are pre-stored in advance, is determined. If the matching indicates that the call request is a legal request, the called server may transmit a plurality of parameters, which are included in the call request and are required for calling the payment API, to the payment API, and the payment API may operate according to the plurality of parameters, and then an operation result output by the payment API is used as a target operation result. If not, the calling request is an illegal request, and then feedback information indicating calling failure is returned to the calling terminal.

In step 403, according to the main channel identifier and the auxiliary channel identifier, querying a preset tree-shaped call relationship corresponding to the main channel identifier to obtain target feature information recorded by the auxiliary channel corresponding to the auxiliary channel identifier in the tree-shaped call relationship, where the tree-shaped call relationship includes the main channel corresponding to the main channel identifier, a plurality of auxiliary channels corresponding to the main channel, and feature information recorded by each auxiliary channel.

In step 404, call feedback information is sent to the calling terminal according to the target feature information and the target operation result, so that the calling terminal displays the calling result according to the call feedback information.

For example, the called server may query, according to the main channel identifier, a preset tree-shaped call relationship corresponding to the main channel identifier, that is, query a preset tree-shaped call relationship corresponding to the main channel identifier included in the call request, in a plurality of tree-shaped call relationships for the payment API. Specifically, the called server may obtain a plurality of preset tree-shaped calling relations for the payment API, and then obtain a main channel identifier of a main channel included in each tree-shaped calling relation in the plurality of tree-shaped calling relations, and further take the tree-shaped calling relation in which the main channel identifier is the main channel of the application name of the calling application as the tree-shaped calling relation corresponding to the main channel identifier included in the calling request, where three subsidiary channels are respectively located under the main channel of the tree-shaped calling relation, where a first subsidiary channel corresponds to the application identifier of the mobile phone application, and feature information recorded by the first subsidiary channel is first postage information; the second subsidiary channel corresponds to the application identifier applied by the tablet personal computer end, and the characteristic information recorded by the second subsidiary channel is second postage information; the third subsidiary channel corresponds to the application identifier of the personal computer side application, and the characteristic information recorded by the third subsidiary channel is third postage information. And then the called server can acquire first postage information recorded by the first auxiliary channel as target characteristic information according to an auxiliary channel identifier included in the calling request, namely an application identifier applied by the mobile phone terminal, further generate calling feedback information according to the target characteristic information and a target operation result, and send the calling feedback information to the calling terminal.

In the technical scheme provided by the embodiment of the disclosure, the called server can record the feature information corresponding to different auxiliary channels by presetting the tree-shaped calling relationship aiming at the target API, and after receiving the calling request of the calling terminal, the called server can query the tree-shaped calling relationship according to the main channel identifier and the auxiliary channel identifier included in the calling request to acquire the feature information corresponding to the current auxiliary channel of the calling terminal, so that the process of acquiring the feature information by the calling terminal is simplified, the efficiency of calling the target API is improved, and the coupling of the called server in the process of calling the API is further reduced.

The implementation is described in detail below by way of several embodiments.

Fig. 5 is an interaction diagram illustrating an application programming interface calling method according to an exemplary embodiment, where the execution subjects are a development terminal, an API management platform, a calling terminal, and a called server, and as shown in fig. 5, the method includes the following steps 501 to 530:

in step 501, the called server issues a plurality of supported APIs to the API management platform according to an instruction of an administrator of the API management platform.

In step 502, the development terminal logs in the API management platform and exposes the APIs distributed on the API management platform, so that a developer of the calling application refers to the APIs and determines whether the calling application needs to call any one of the APIs.

In step 503, when the developer of the calling application determines that the calling application to be developed needs to call a target API in the APIs, the development terminal obtains a first registration instruction, and sends first registration information to the API management platform in response to the first registration instruction, where the first registration information includes an application name of the calling application and an interface identifier of the target API.

In step 504, after receiving the first registration information, the API management platform presents the first registration information, so that an administrator of the API management platform can check the first registration information in time.

In step 505, the API management platform obtains first audit information, and determines whether the first registration information passes the audit according to the first audit information; if the first registration information is not approved, go to step 506; if the first registration information has passed the audit, go to step 507.

In step 506, the API management platform sends an audit failure prompt to the development terminal.

In step 507, the API management platform creates a main channel of the target API according to the application name included in the first registration information, where the main channel identifier of the main channel is the same as the application name.

In step 508, the API management platform assigns a primary channel token for the primary channel for a target API corresponding to the interface identifier included in the first registration information.

In step 509, the API management platform sends first feedback information to the development terminal according to the main channel identifier of the main channel and the main channel token.

In step 510, the development terminal presents the first feedback information for the developer to review.

In step 511, the development terminal obtains a second registration instruction, and sends second registration information to the API management platform in response to the second registration instruction, where the second registration information includes a plurality of sub-channel identifiers corresponding to the main channel identifier and feature information corresponding to each sub-channel identifier.

In step 512, after receiving the second registration information, the API management platform displays the second registration information, so that an administrator of the API management platform can check the second registration information in time.

In step 513, the API management platform obtains second audit information, and determines whether the second registration information passes the audit according to the second audit information; if the second registration information is not approved, go to step 506; if the second registration information has passed the audit, go to step 514.

In step 514, the API management platform creates a plurality of auxiliary channels respectively corresponding to the plurality of auxiliary channel identifiers included in the second registration information in the previously created main channel, where each auxiliary channel records feature information corresponding to the auxiliary channel, so as to form a tree call relationship.

In step 515, the API management platform assigns a secondary channel key for each secondary channel.

In step 516, the API management platform sends second feedback information to the development terminal, where the second feedback information includes a sub-channel key allocated to each sub-channel.

In step 517, the development terminal displays the second feedback information for the developer to refer to.

In step 518, the API management platform synchronizes the created tree call relationship, the primary channel token assigned to the primary channel, and the channel key assigned to each secondary channel to the called service.

In step 519, when the calling terminal needs to call the target API, the calling terminal sends a call request to the called server, where the call request includes a current primary channel identifier, a primary channel token, a secondary channel identifier, a secondary channel key, an interface identifier of the target API, and a plurality of parameters required for calling the target API.

In step 520, the called server performs a request token check on the calling application, and determines whether the main channel token and the auxiliary channel key included in the calling request are legal; if the main channel token and the auxiliary channel key included in the call request are not legal, execute step 521; if the primary channel token and the secondary channel key included in the invocation request are both valid, step 522 is performed.

In step 521, the invoked server returns feedback information indicating that the invocation failed to the invoking terminal.

In step 522, the called server performs interface authentication on the call instruction, and determines whether the call terminal has the right to call the target API; if the calling terminal has no authority to call the target API, executing step 521; if the calling terminal has the authority to call the target API, step 523 is executed.

In step 523, the called server checks the calling parameter and determines whether the calling application includes a preset parameter, where the preset parameter is a legal parameter necessary for calling the target API; if the calling application does not include the default parameters, go to step 521; if the calling application includes the default parameters, step 524 is performed.

In step 524, the called server transmits a plurality of parameters included by the calling application and required for calling the target API to the target API, so that the target API operates according to the plurality of parameters.

In step 525, the called server obtains the target operation result returned by the target API.

In step 526, the called server obtains a tree-shaped calling relationship corresponding to the main channel identifier according to the main channel identifier included in the calling request.

In step 527, the called server obtains, according to the auxiliary channel identifier included in the call request, feature information recorded by the auxiliary channel corresponding to the auxiliary channel identifier in the tree-shaped call relationship as target feature information.

In step 528, the called server generates calling feedback information according to the target operation result and the target characteristic information.

In step 529, the called server sends the call feedback information to the calling terminal.

In step 530, the calling terminal displays the calling result according to the operation result and the feature information included in the calling feedback information.

The embodiment of the disclosure provides an application programming interface calling method, an API management platform can form a tree-shaped calling relation according to information included in first registration information and second registration information sent by a development terminal, the tree-shaped calling relation is synchronized to a called server, and the tree-shaped calling relation includes a main channel aiming at a payment API, a plurality of auxiliary channels corresponding to the main channel and characteristic information recorded by each auxiliary channel. After receiving a calling request of a calling terminal, the called server can query the tree-shaped calling relationship according to the main channel identifier and the auxiliary channel identifier included in the calling request to acquire the characteristic information corresponding to the current auxiliary channel of the calling terminal, so that the process of acquiring the characteristic information by the calling terminal is simplified, the efficiency of calling a target API is improved, and the coupling of the called server in the process of calling the API is further reduced.

The following are embodiments of the disclosed apparatus that may be used to perform embodiments of the disclosed methods.

Fig. 6a is a schematic diagram illustrating a structure of an api calling apparatus 60 according to an exemplary embodiment, where the apparatus 60 may be implemented as part of or all of an electronic device through software, hardware, or a combination of both. As shown in fig. a, the api calling apparatus 60 includes a first receiving module 601, a calling module 602, a querying module 603 and a first sending module 604.

The first receiving module 601 is configured to receive a call request sent by a call terminal, where the call request includes a main channel identifier, an auxiliary channel identifier, an interface identifier of a target API to be called, and multiple parameters required for calling the target API.

The calling module 602 is configured to call the target API corresponding to the interface identifier according to the multiple parameters included in the call request and required for calling the target API, and obtain a target operation result of the target API.

A query module 603 configured to query a preset tree-shaped call relationship corresponding to the main channel identifier according to the main channel identifier and the auxiliary channel identifier, and obtain target feature information recorded in the tree-shaped call relationship and the auxiliary channel corresponding to the auxiliary channel identifier, where the tree-shaped call relationship includes the main channel corresponding to the main channel identifier, a plurality of auxiliary channels corresponding to the main channel, and feature information recorded in each auxiliary channel.

A first sending module 604, configured to send, according to the target feature information and the target operation result, call feedback information to the calling terminal, so that the calling terminal displays the calling result according to the call feedback information.

In one embodiment, as shown in fig. 6b, the calling module 602 includes an authentication sub-module 6021 and a first calling sub-module 6022.

The authentication submodule 6021 is configured to perform interface authentication on the call request according to the main channel identifier and the auxiliary channel identifier.

The first calling sub-module 6022 is configured to, if the interface authentication indicates that the calling terminal has the authority to call the target API, call the target API corresponding to the interface identifier according to a plurality of parameters included in the call request and required for calling the target API, and obtain a target operation result of the target API.

In one embodiment, as shown in FIG. 6c, the calling module 602 includes a determination sub-module 6023 and a second calling sub-module 6024.

The determining submodule 6023 is configured to determine whether the call request includes a preset parameter, where the preset parameter is a legal parameter necessary for calling the target API.

The second calling sub-module 6024 is configured to, if the call request includes the preset parameter, call the target API corresponding to the interface identifier according to the plurality of parameters included in the call request and required for calling the target API, and obtain a target operation result of the target API.

In one embodiment, as shown in FIG. 6d, the calling module 602 includes a check submodule 6025 and a third calling submodule 6026.

The verification submodule 6025 is configured to perform request token verification on the invocation request according to the primary channel token and the secondary channel key included in the invocation request.

The third calling sub-module 6026 is configured to, if the request token verification indicates that the calling request is a legal request, call the target API corresponding to the interface identifier according to the multiple parameters, which are included in the calling request and are required to call the target API, and obtain a target operation result of the target API.

In one embodiment, as shown in fig. 6e, the apparatus 60 further comprises a second receiving module 605 and a synchronization module 606.

The second receiving module 605 is configured to receive a synchronization instruction sent by the API management platform, where the synchronization instruction includes the tree call relationship.

And a synchronization module 606, configured to store the tree call relationship according to the synchronization instruction.

The embodiment of the disclosure provides an application programming interface calling device, which can record feature information corresponding to different auxiliary channels by presetting a tree-shaped calling relationship for a target API, and after receiving a calling request of a calling terminal, can query the tree-shaped calling relationship according to a main channel identifier and an auxiliary channel identifier included in the calling request to acquire the feature information corresponding to the current auxiliary channel of the calling terminal, thereby simplifying the process of acquiring the feature information by the calling terminal, improving the efficiency of calling the target API, and further reducing the coupling of a called server in the process of calling the API.

Fig. 7 is a schematic diagram illustrating a structure of an api calling apparatus 70 according to an exemplary embodiment, where the apparatus 70 may be implemented as part of or all of an electronic device through software, hardware, or a combination of both. As shown in fig. 7, the api calling apparatus 70 includes a second sending module 701, a third receiving module 702 and a displaying module 703.

The second sending module 701 is configured to send a call request to a called server, where the call request includes a main channel identifier of the call terminal, an auxiliary channel identifier, an interface identifier of a target API to be called, and multiple parameters required for calling the target API.

A third receiving module 702, configured to receive call feedback information sent by the called server, where the call feedback information includes a target operation result obtained by calling the target API and target feature information of an auxiliary channel record corresponding to the auxiliary channel identifier in a tree-shaped call relationship preset by the called server, where the tree-shaped call relationship includes a main channel corresponding to the main channel identifier, multiple auxiliary channels corresponding to the main channel, and feature information of each auxiliary channel record.

And a display module 703, configured to display the invocation result according to the target operation result and the target feature information.

The embodiment of the disclosure provides an application programming interface calling device, and the terminal can carry a main channel identifier and an auxiliary channel identifier in a calling request, so that a called server can query a tree-shaped calling relationship according to the main channel identifier and the auxiliary channel identifier to obtain characteristic information corresponding to a current auxiliary channel of the calling terminal, a scheme of calling a target API and simultaneously obtaining the characteristic information is realized, a process of obtaining the characteristic information by the calling terminal is simplified, the efficiency of calling the target API is improved, and further the coupling of the called server in the process of calling the API is reduced.

Fig. 8 is a schematic diagram illustrating a structure of an api calling apparatus 80 according to an exemplary embodiment, where the apparatus 80 may be implemented as part of or all of an electronic device through software, hardware, or a combination of both. As shown in fig. 8, the api call apparatus 80 includes a first obtaining module 801, a fourth receiving module 802 and a second obtaining module 803.

The first obtaining module 801 is configured to obtain a first registration instruction, and send first registration information to an API management platform in response to the first registration instruction, where the first registration information includes an application name of a calling application and an interface identifier of a target API that the calling application needs to call, so that the API management platform creates a main channel for the target API, where the main channel identifier of the main channel is the same as the application name, and the development terminal is a terminal for developing the calling application;

a fourth receiving module 802, configured to receive and display first feedback information sent by the API management platform, where the first feedback information includes the main channel identifier;

second acquisition module 803 for acquire second registration instruction, respond to second registration instruction sends second registration information to API management platform, second registration information include with a plurality of subsidiary channel identifications that main channel identification corresponds to and the characteristic information that every subsidiary channel identification corresponds, so that API management platform basis a plurality of subsidiary channel identifications, and the characteristic information that every subsidiary channel identification corresponds create under the main channel respectively with a plurality of subsidiary channels that a plurality of subsidiary channel identifications correspond, every subsidiary channel record has the characteristic information rather than corresponding, forms tree-shaped calling relation.

The embodiment of the disclosure provides an application programming interface calling device, which can send first registration information and second registration information to an API management platform according to an instruction of a developer calling an application, so that the API management platform forms a tree-shaped calling relationship according to contents included in the first registration information and the second registration information, and after the API management platform synchronously stores the tree-shaped calling relationship in a called server, a calling terminal can obtain feature information while calling a target API, so that the process of obtaining the feature information by the calling terminal is simplified, the efficiency of calling the target API is improved, and further, the coupling of the called server in the process of calling the API is reduced.

Fig. 9a is a schematic diagram illustrating a structure of an api calling apparatus 90 according to an exemplary embodiment, where the apparatus 90 may be implemented as part of or all of an electronic device through software, hardware, or a combination of the two. As shown in fig. 9a, the api calling apparatus 90 comprises a fifth receiving module 901, a first creating module 902, a third sending module 903, a sixth receiving module 904, a second creating module 905 and a fourth sending module 906.

The fifth receiving module 901 is configured to receive first registration information sent by a development terminal, where the first registration information includes an application name of a calling application and an interface identifier of a target API that the calling application needs to call, and the development terminal is a terminal for developing the calling application.

A first creating module 902, configured to create a main channel of the target API according to the application name included in the first registration information, where a main channel identifier of the main channel is the same as the application name.

A third sending module 903, configured to send first feedback information to the development terminal, where the first feedback information includes the main channel identifier, so that the development terminal obtains a plurality of auxiliary channel identifiers corresponding to the main channel identifier and characteristic information corresponding to each auxiliary channel identifier.

A sixth receiving module 904, configured to receive second registration information sent by the development terminal, where the second registration information includes a plurality of secondary channel identifiers corresponding to the primary channel identifiers, and feature information corresponding to each secondary channel identifier.

The second creating module 905 is configured to create, according to the multiple auxiliary channel identifiers included in the second registration information and the feature information corresponding to each auxiliary channel identifier, multiple auxiliary channels corresponding to the multiple auxiliary channel identifiers respectively under the main channel, where each auxiliary channel is recorded with the feature information corresponding thereto, so as to form a tree-shaped calling relationship.

A fourth sending module 906, configured to send a synchronization instruction to the called server according to the tree call relationship, so that the called server stores the tree call relationship synchronously.

In one embodiment, as shown in fig. 9b, the first creation module 902 includes a first determination submodule 9021 and a first creation submodule 9022.

The first determining sub-module 9021 is configured to determine whether the first registration information passes the audit.

A first creating sub-module 9022, configured to create, if the first registration information passes the audit, a main channel of the target API according to the application name included in the first registration information.

In one embodiment, as shown in fig. 9c, the second creating module 905 includes a second determining submodule 9051 and a second creating submodule 9052.

The second determining sub-module 9051 is configured to determine whether the second registration information passes the audit.

And a second creating sub-module 9052, configured to create, if the second registration information passes the audit, a plurality of auxiliary channels respectively corresponding to the plurality of auxiliary channel identifiers under the main channel according to the plurality of auxiliary channel identifiers included in the second registration information and the feature information corresponding to each auxiliary channel identifier, where each auxiliary channel records the feature information corresponding to each auxiliary channel identifier, and a tree-shaped calling relationship is formed.

In one embodiment, as shown in fig. 9d, the apparatus 90 further includes a first allocation module 907 and a second allocation module 908, and the fourth sending module 906 includes a sending submodule 9061.

Wherein, the first allocating module 907 is configured to allocate a main channel token for the target API to the main channel;

a second allocating module 908 for allocating a secondary channel key for each secondary channel of the plurality of secondary channels;

and the sending submodule 9061 is configured to send a synchronization instruction to the called server according to the tree-shaped call relationship, the main channel token, and the auxiliary channel key of each auxiliary channel, so that the called server synchronously stores the tree-shaped call relationship, the main channel token, and the auxiliary channel key of each auxiliary channel.

The embodiment of the disclosure provides an application programming interface calling device, which forms a tree-shaped calling relationship according to contents included in first registration information and second registration information, and synchronizes the tree-shaped calling relationship to a called server, so that a calling terminal can acquire feature information while calling a target API, the process of acquiring the feature information by the calling terminal is simplified, the efficiency of calling the target API is improved, and the coupling of the called server in the process of calling the API is reduced.

The embodiment of the present disclosure provides an application programming interface calling device, which includes:

a first processor;

a first memory for storing first processor-executable instructions;

wherein the first processor is configured to:

In one embodiment, the processor may be further configured to: performing interface authentication on the calling request according to the main channel identifier and the auxiliary channel identifier; if the interface authentication indicates that the calling terminal has the authority to call the target API, calling the target API corresponding to the interface identification according to a plurality of parameters required for calling the target API and included in the calling request, and acquiring a target operation result of the target API.

In one embodiment, the processor may be further configured to: determining whether the calling request comprises a preset parameter, wherein the preset parameter is a legal parameter necessary for calling the target API; if the calling request comprises the preset parameters, calling a target API corresponding to the interface identifier according to a plurality of parameters which are included in the calling request and are required for calling the target API, and acquiring a target operation result of the target API.

In one embodiment, the processor may be further configured to: according to the main channel token and the auxiliary channel key included in the calling request, carrying out request token verification on the calling request; if the request token verification indicates that the calling request is a legal request, calling a target API corresponding to the interface identifier according to a plurality of parameters required for calling the target API and included in the calling request, and acquiring a target operation result of the target API.

In one embodiment, the processor may be further configured to: receiving a synchronization instruction sent by an API management platform, wherein the synchronization instruction comprises the tree call relation; and storing the tree-shaped calling relation according to the synchronous instruction.

a second processor;

a second memory for storing second processor-executable instructions;

wherein the second processor is configured to:

a third processor;

a third memory for storing third processor-executable instructions;

wherein the third processor is configured to:

a fourth processor;

a fourth memory for storing fourth processor-executable instructions;

wherein the fourth processor is configured to:

In one embodiment, the processor may be further configured to: determining whether the first registration information passes an audit; and if the first registration information passes the examination, creating a main channel of the target API according to the application name included in the first registration information.

In one embodiment, the processor may be further configured to: determining whether the second registration information passes an audit; and if the second registration information passes the audit, according to a plurality of auxiliary channel identifications included in the second registration information and the characteristic information corresponding to each auxiliary channel identification, creating a plurality of auxiliary channels respectively corresponding to the plurality of auxiliary channel identifications under the main channel, wherein each auxiliary channel records the characteristic information corresponding to each auxiliary channel, and forming a tree-shaped calling relationship.

In one embodiment, the processor may be further configured to: distributing a primary channel token aiming at the target API for the primary channel; assigning an auxiliary channel key to each of the plurality of auxiliary channels; and sending a synchronous instruction to the called server according to the tree-shaped calling relationship, the main channel token and the auxiliary channel key of each auxiliary channel, so that the called server synchronously stores the tree-shaped calling relationship, the main channel token and the auxiliary channel key of each auxiliary channel.

With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.

Fig. 10 is a block diagram illustrating a structure of an api call apparatus 100 according to an exemplary embodiment, where the apparatus 100 is suitable for a terminal device. For example, the apparatus 100 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, an exercise device, a personal digital assistant, and the like.

The apparatus 100 may include one or more of the following components: processing component 1002, memory 1004, power component 1006, multimedia component 1008, audio component 1010, input/output (I/O) interface 1012, sensor component 1014, and communications component 1016.

The processing component 1002 generally controls the overall operation of the device 100, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 1002 may include one or more processors 1020 to execute instructions to perform all or a portion of the steps of the methods described above. Further, processing component 1002 may include one or more modules that facilitate interaction between processing component 1002 and other components. For example, the processing component 1002 may include a multimedia module to facilitate interaction between the multimedia component 1008 and the processing component 1002.

The memory 1004 is configured to store various types of data to support operations at the apparatus 100. Examples of such data include instructions for any application or method operating on device 100, contact data, phonebook data, messages, pictures, videos, and so forth. The memory 1004 may be implemented by any type or combination of volatile or non-volatile memory devices, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.

The power supply component 1006 provides power to the various components of the device 100. The power components 1006 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device 100.

The multimedia component 1008 includes a screen that provides an output interface between the device 100 and a user. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 1008 includes a front facing camera and/or a rear facing camera. The front camera and/or the rear camera may receive external multimedia data when the device 100 is in an operating mode, such as a shooting mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

The audio component 1010 is configured to output and/or input audio signals. For example, audio component 1010 includes a Microphone (MIC) configured to receive external audio signals when apparatus 100 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal may further be stored in the memory 1004 or transmitted via the communication component 1016. In some embodiments, audio component 1010 further includes a speaker for outputting audio signals.

I/O interface 1012 provides an interface between processing component 1002 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: a home button, a volume button, a start button, and a lock button.

The sensor assembly 1014 includes one or more sensors for providing various aspects of status assessment for the device 100. For example, the sensor assembly 1014 may detect an open/closed state of the device 100, the relative positioning of components, such as a display and keypad of the device 100, the sensor assembly 1014 may also detect a change in position of the device 100 or a component of the device 100, the presence or absence of user contact with the device 100, orientation or acceleration/deceleration of the device 100, and a change in temperature of the device 100. The sensor assembly 1014 may include a proximity sensor configured to detect the presence of a nearby object in the absence of any physical contact. The sensor assembly 1014 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 1014 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

The communication component 1016 is configured to facilitate communications between the apparatus 100 and other devices in a wired or wireless manner. The device 100 may access a wireless network based on a communication standard, such as WiFi,2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 1016 receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 1016 further includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, ultra Wideband (UWB) technology, bluetooth (BT) technology, and other technologies.

In an exemplary embodiment, the apparatus 100 may be implemented by one or more Application Specific Integrated Circuits (ASICs), digital Signal Processors (DSPs), digital Signal Processing Devices (DSPDs), programmable Logic Devices (PLDs), field Programmable Gate Arrays (FPGAs), controllers, micro-controllers, microprocessors, or other electronic components for performing the above-described methods.

In an exemplary embodiment, a non-transitory computer readable storage medium comprising instructions, such as the memory 1004 comprising instructions, executable by the processor 1020 of the apparatus 100 to perform the above-described method is also provided. For example, the non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.

FIG. 11 is a block diagram illustrating an apparatus 110 for application programming interface invocation in accordance with an exemplary embodiment. For example, the apparatus 110 may be provided as a server. The apparatus 110 comprises a processing component 1102, which further comprises one or more processors, and memory resources, represented by memory 1103, for storing instructions, e.g., applications, that are executable by the processing component 1102. The application stored in the memory 1103 may include one or more modules that each correspond to a set of instructions. Further, the processing component 1102 is configured to execute instructions to perform the above-described methods.

The device 110 may also include a power component 1106 configured to perform power management of the device 110, a wired or wireless network interface 1105 configured to connect the device 110 to a network, and an input output (I/O) interface 1108. The device 110 may operate based on an operating system stored in the memory 1103, such as Windows Server, mac OS XTM, unixTM, linuxTM, freeBSDTM, or the like.

The disclosed embodiment provides a non-transitory computer readable storage medium, and when instructions in the storage medium are executed by a processor of the apparatus 100, the apparatus 100 is enabled to execute the above-mentioned method for calling an application programming interface on a terminal side, the method includes:

The disclosed embodiments provide a non-transitory computer-readable storage medium, where instructions executed by a processor of the device 110 enable the device 110 to perform the above-mentioned called server-side application programming interface calling method, where the method includes:

In an embodiment, the calling the target API corresponding to the interface identifier according to a plurality of parameters included in the call request and required for calling the target API, and obtaining the target operation result of the target API includes: performing interface authentication on the calling request according to the main channel identifier and the auxiliary channel identifier; if the interface authentication indicates that the calling terminal has the authority to call the target API, calling the target API corresponding to the interface identification according to a plurality of parameters required for calling the target API and included in the calling request, and acquiring a target operation result of the target API.

In an embodiment, the calling the target API corresponding to the interface identifier according to a plurality of parameters included in the call request and required for calling the target API, and obtaining the target operation result of the target API includes: determining whether the calling request comprises a preset parameter, wherein the preset parameter is a legal parameter necessary for calling the target API; if the calling request comprises the preset parameters, calling a target API corresponding to the interface identifier according to a plurality of parameters required for calling the target API and included in the calling request, and acquiring a target operation result of the target API.

In one embodiment, the invocation request further includes a primary channel token and a secondary channel key; the calling the target API corresponding to the interface identifier according to the plurality of parameters required for calling the target API included in the calling request, and acquiring the target operation result of the target API comprises: according to the main channel token and the auxiliary channel key included in the calling request, carrying out request token verification on the calling request; if the request token verification indicates that the calling request is a legal request, calling a target API corresponding to the interface identifier according to a plurality of parameters required for calling the target API and included in the calling request, and acquiring a target operation result of the target API.

In one embodiment, the method further comprises: receiving a synchronization instruction sent by an API management platform, wherein the synchronization instruction comprises the tree call relation; and storing the tree-shaped calling relation according to the synchronous instruction.

The embodiment of the present disclosure provides a non-transitory computer-readable storage medium, wherein when instructions in the storage medium are executed by a processor of a development terminal, the development terminal is enabled to execute an application programming interface calling method on the development terminal side, and the method includes:

acquiring a first registration instruction, and sending first registration information to an API (application programming interface) management platform in response to the first registration instruction, wherein the first registration information comprises an application name of a calling application and an interface identifier of a target API required to be called by the calling application, so that the API management platform creates a main channel for the target API, the main channel identifier of the main channel is the same as the application name, and the development terminal is a terminal for developing the calling application;

The disclosed embodiments provide a non-transitory computer-readable storage medium, where when instructions in the storage medium are executed by a processor of an API management platform, the storage medium enables the API management platform to execute an API call method on an API management platform side, where the method includes:

In one embodiment, the creating a main channel of the target API according to the application name included in the first registration information includes: determining whether the first registration information passes an audit; and if the first registration information passes the audit, creating a main channel of the target API according to the application name included in the first registration information.

In an embodiment, the creating, according to the multiple secondary channel identifiers and the feature information corresponding to each secondary channel identifier included in the second registration information, multiple secondary channels respectively corresponding to the multiple secondary channel identifiers in the primary channel, where each secondary channel records feature information corresponding to the secondary channel identifier, and forming a tree-shaped invocation relationship includes: determining whether the second registration information passes an audit; and if the second registration information passes the audit, according to a plurality of auxiliary channel identifications included in the second registration information and the characteristic information corresponding to each auxiliary channel identification, creating a plurality of auxiliary channels respectively corresponding to the plurality of auxiliary channel identifications under the main channel, wherein each auxiliary channel records the characteristic information corresponding to each auxiliary channel, and forming a tree-shaped calling relationship.

In one embodiment, the method further comprises: distributing a primary channel token aiming at the target API for the primary channel; assigning an auxiliary channel key to each of the plurality of auxiliary channels; the sending a synchronization instruction to the called server according to the tree call relation so that the called server synchronously stores the tree call relation comprises: and sending a synchronous instruction to the called server according to the tree-shaped calling relationship, the main channel token and the auxiliary channel key of each auxiliary channel, so that the called server synchronously stores the tree-shaped calling relationship, the main channel token and the auxiliary channel key of each auxiliary channel.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It will be understood that the present disclosure is not limited to the precise arrangements that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. An application programming interface calling method applied to a called server, comprising:

2. The method according to claim 1, wherein the calling the target API corresponding to the interface identifier according to a plurality of parameters included in the call request and required for calling the target API, and obtaining the target operation result of the target API comprises:

3. The method according to claim 1, wherein the calling the target API corresponding to the interface identifier according to a plurality of parameters included in the call request and required for calling the target API, and the obtaining the target operation result of the target API comprises:

4. The method of claim 1, wherein the invocation request further comprises a primary channel token and a secondary channel key; the calling the target API corresponding to the interface identifier according to the plurality of parameters, included in the calling request, required for calling the target API, and the obtaining of the target operation result of the target API comprises the following steps:

if the request token verification indicates that the calling request is a legal request, calling a target API corresponding to the interface identifier according to a plurality of parameters which are included in the calling request and are required for calling the target API, and acquiring a target operation result of the target API.

5. The method of any one of claims 1 to 4, further comprising:

6. An application programming interface calling method is applied to a calling terminal and comprises the following steps:

7. An application programming interface calling method is applied to a development terminal and comprises the following steps:

and acquiring a second registration instruction, responding to the second registration instruction, and sending second registration information to the API management platform, wherein the second registration information comprises a plurality of auxiliary channel identifications corresponding to the main channel identifications and characteristic information corresponding to each auxiliary channel identification, so that the API management platform can establish a plurality of auxiliary channels corresponding to the plurality of auxiliary channel identifications and each auxiliary channel identification under the main channel, and each auxiliary channel is recorded with the corresponding characteristic information to form a tree-shaped calling relation.

8. An application programming interface calling method applied to an API management platform comprises the following steps:

receiving second registration information sent by the development terminal, wherein the second registration information comprises a plurality of auxiliary channel identifications corresponding to the main channel identification and characteristic information corresponding to each auxiliary channel identification;

9. The method of claim 8, wherein the creating the main channel of the target API according to the application name included in the first registration information comprises:

determining whether the first registration information passes an audit;

and if the first registration information passes the audit, creating a main channel of the target API according to the application name included in the first registration information.

10. The method according to claim 8, wherein according to a plurality of secondary channel identifiers included in the second registration information and feature information corresponding to each secondary channel identifier, creating a plurality of secondary channels respectively corresponding to the plurality of secondary channel identifiers under the primary channel, each secondary channel recording feature information corresponding thereto, and forming a tree-shaped calling relationship includes:

determining whether the second registration information passes an audit;

11. The method according to any one of claims 8 to 10, further comprising:

the sending a synchronization instruction to the called server according to the tree call relation so that the called server synchronously stores the tree call relation comprises:

12. An API call apparatus, comprising:

the calling module is used for calling the target API corresponding to the interface identifier according to a plurality of parameters required by calling the target API and included in the calling request, and acquiring a target operation result of the target API;

and the first sending module is used for sending calling feedback information to the calling terminal according to the target characteristic information and the target operation result so as to facilitate the calling terminal to display the calling result according to the calling feedback information.

13. The apparatus of claim 12, wherein the means for invoking comprises:

the authentication submodule is used for carrying out interface authentication on the calling request according to the main channel identifier and the auxiliary channel identifier;

14. The apparatus of claim 12, wherein the means for invoking comprises:

the determining submodule is used for determining whether the calling request comprises preset parameters or not, wherein the preset parameters are legal parameters necessary for calling the target API;

15. The apparatus of claim 12, wherein the means for invoking comprises:

16. The apparatus of any one of claims 12 to 15, further comprising:

17. An API-calling apparatus, comprising:

the second sending module is used for sending a calling request to a called server, wherein the calling request comprises a main channel identifier and an auxiliary channel identifier of a calling terminal, an interface identifier of a target API needing to be called and a plurality of parameters required by calling the target API;

a third receiving module, configured to receive call feedback information sent by the called server, where the call feedback information includes a target operation result obtained by calling the target API and target feature information of an auxiliary channel record corresponding to the auxiliary channel identifier in a tree-shaped call relationship preset by the called server, and the tree-shaped call relationship includes a main channel corresponding to the main channel identifier, multiple auxiliary channels corresponding to the main channel, and feature information recorded by each auxiliary channel;

18. An API-calling apparatus, comprising:

the second acquisition module is used for acquiring a second registration instruction, responding to the second registration instruction and sending second registration information to the API management platform, wherein the second registration information comprises a plurality of auxiliary channel identifications corresponding to the main channel identifications and characteristic information corresponding to each auxiliary channel identification, so that the API management platform can be used for establishing a plurality of auxiliary channel identifications and characteristic information corresponding to each auxiliary channel identification under the main channel, and each auxiliary channel is recorded with the corresponding characteristic information to form a tree-shaped calling relationship.

19. An API call apparatus, comprising:

a third sending module, configured to send first feedback information to the development terminal, where the first feedback information includes the main channel identifier, so that the development terminal obtains multiple auxiliary channel identifiers corresponding to the main channel identifier and feature information corresponding to each auxiliary channel identifier;

a second creating module, configured to create, according to the multiple auxiliary channel identifiers and feature information corresponding to each auxiliary channel identifier that are included in the second registration information, multiple auxiliary channels that respectively correspond to the multiple auxiliary channel identifiers in the main channel, where each auxiliary channel records feature information corresponding to the auxiliary channel identifier, and forms a tree-shaped calling relationship;

20. The apparatus of claim 19, wherein the first creation module comprises:

the first determining sub-module is used for determining whether the first registration information passes the audit;

21. The apparatus of claim 19, wherein the second creating module comprises:

22. The apparatus of any one of claims 19 to 21, further comprising:

a second allocating module for allocating a secondary channel key to each of the plurality of secondary channels;

the fourth sending module comprises:

23. An API call apparatus, comprising:

a first processor;

a first memory for storing first processor-executable instructions;

wherein the first processor is configured to:

24. An API-calling apparatus, comprising:

a second processor;

a second memory for storing second processor-executable instructions;

wherein the second processor is configured to:

sending a calling request to a called server, wherein the calling request comprises a main channel identifier and an auxiliary channel identifier of a calling terminal, an interface identifier of a target API needing to be called, and a plurality of parameters required by calling the target API;

25. An API call apparatus, comprising:

a third processor;

a third memory for storing third processor-executable instructions;

wherein the third processor is configured to:

acquiring a first registration instruction, and sending first registration information to an API (application programming interface) management platform in response to the first registration instruction, wherein the first registration information comprises an application name of a calling application and an interface identifier of a target API required to be called by the calling application, so that the API management platform creates a main channel aiming at the target API, the main channel identifier of the main channel is the same as the application name, and a development terminal is a terminal for developing the calling application;

26. An API-calling apparatus, comprising:

a fourth processor;

a fourth memory for storing fourth processor-executable instructions;

wherein the fourth processor is configured to:

according to the plurality of auxiliary channel identifications included in the second registration information and the characteristic information corresponding to each auxiliary channel identification, a plurality of auxiliary channels respectively corresponding to the plurality of auxiliary channel identifications are established under the main channel, and each auxiliary channel is recorded with the corresponding characteristic information to form a tree-shaped calling relationship;

27. A computer-readable storage medium having stored thereon computer instructions, which when executed by a processor, perform the steps of the method of any one of claims 1 to 5.

28. A computer-readable storage medium having stored thereon computer instructions, which when executed by a processor, perform the steps of the method of claim 6.

29. A computer-readable storage medium having stored thereon computer instructions, which when executed by a processor, perform the steps of the method of claim 7.

30. A computer-readable storage medium having stored thereon computer instructions, which when executed by a processor, perform the steps of the method of any one of claims 8 to 11.