CN106873958B - Calling method and device of application programming interface - Google Patents
Calling method and device of application programming interface Download PDFInfo
- Publication number
- CN106873958B CN106873958B CN201610529818.1A CN201610529818A CN106873958B CN 106873958 B CN106873958 B CN 106873958B CN 201610529818 A CN201610529818 A CN 201610529818A CN 106873958 B CN106873958 B CN 106873958B
- Authority
- CN
- China
- Prior art keywords
- api
- identifier
- identification
- carried
- call
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 27
- 238000012545 processing Methods 0.000 claims description 9
- 238000000605 extraction Methods 0.000 claims description 2
- 239000008186 active pharmaceutical agent Substances 0.000 description 12
- 230000006870 function Effects 0.000 description 12
- 238000010586 diagram Methods 0.000 description 10
- 238000004590 computer program Methods 0.000 description 7
- 238000012795 verification Methods 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 238000011161 development Methods 0.000 description 2
- 230000018109 developmental process Effects 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- SPBWHPXCWJLQRU-FITJORAGSA-N 4-amino-8-[(2r,3r,4s,5r)-3,4-dihydroxy-5-(hydroxymethyl)oxolan-2-yl]-5-oxopyrido[2,3-d]pyrimidine-6-carboxamide Chemical compound C12=NC=NC(N)=C2C(=O)C(C(=O)N)=CN1[C@@H]1O[C@H](CO)[C@@H](O)[C@H]1O SPBWHPXCWJLQRU-FITJORAGSA-N 0.000 description 1
- 102100039986 Apoptosis inhibitor 5 Human genes 0.000 description 1
- 102100021677 Baculoviral IAP repeat-containing protein 2 Human genes 0.000 description 1
- 101000959871 Homo sapiens Apoptosis inhibitor 5 Proteins 0.000 description 1
- 101000896157 Homo sapiens Baculoviral IAP repeat-containing protein 2 Proteins 0.000 description 1
- 230000032683 aging Effects 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4488—Object-oriented
- G06F9/449—Object-oriented method invocation or resolution
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Telephonic Communication Services (AREA)
Abstract
The application discloses a calling method and a calling device of an application programming interface, wherein an API on an open platform is divided into a plurality of API sets, and a corresponding relation between each API set identifier and a user identifier of a third-party application is established.
Description
Technical Field
The present application relates to the field of information technologies, and in particular, to a method and an apparatus for calling an application programming interface.
Background
An Application Programming Interface (API) is code that a computer operating system or a library provides to an Application program for accessing, and is mainly used for allowing an Application program developer to access a set of routine functions without considering the underlying source code or understanding the details of its internal working mechanism. In the internet era, services of a software system are packaged into a series of computer-recognizable data interfaces which are opened for third-party developers to use, the behavior is called open API, and a platform for providing the open API is called an open platform.
A large number of APIs are stored on the open platform, the functions realized by each API are different, and various third-party applications developed based on the open platform realize the functions of the third-party applications by calling the APIs with specific functions. In order to ensure the security of the open platform, different third-party applications need to be strictly managed to call the API, and some illegal calls of the third-party applications exceeding the API need to be intercepted.
Therefore, the existing API calling method requires various third-party applications to register and acquire user identifiers on the open platform, a user of the third-party application can sign with the open platform through the registered user identifiers to agree on the APIs that the third-party application can call, and after signing, the open platform establishes a corresponding relationship between each API that the third-party application can call and the user identifier of the third-party application. When a third-party application initiates an API call request to the open platform, which API needs to be called needs to be indicated, the open platform queries whether all user identifications corresponding to the API include the user identification of the third-party application, if so, the call is allowed, otherwise, the call is not allowed.
However, with the rapid development of the open platform, each API corresponds to a huge number of user identifiers, the open platform not only needs to store a large number of corresponding relationships between APIs and user identifiers, but also needs to traverse all APIs corresponding to the user identifiers for each API call request to determine whether the call request is legal, which occupies a large amount of resources of the open platform server. Moreover, as the number of third-party applications developed based on the open platform increases and various third-party applications are used more and more, the open platform often receives a large number of API call requests within a short time, and if all the APIs associated with the user identifier need to be traversed for each API call request, a server of the open platform is likely to be congested or even down.
It can be seen that the calling method for API in the prior art may cause a great pressure on the server.
Disclosure of Invention
The embodiment of the application programming interface calling method and device is used for solving the problem that the existing API calling technology causes great pressure on a server.
The application programming interface calling method provided by the embodiment of the application comprises the following steps:
receiving an Application Programming Interface (API) calling request;
extracting user identifiers, API identifiers and API set identifiers carried in the API call request, wherein each API set identifier corresponds to a pre-divided API set, and each API set at least comprises one API;
when determining that the API set identification carried in the API call request has a corresponding relationship with the user identification and the API set corresponding to the API set identification carried in the API call request comprises the API corresponding to the API identification, allowing to call the API corresponding to the API identification;
and refusing to call the API corresponding to the API identification when determining that the API set identification carried in the API call request does not have a corresponding relationship with the user identification or the API set corresponding to the API set identification carried in the API call request does not include the API corresponding to the API identification.
An application programming interface calling device provided in an embodiment of the present application includes:
the receiving module receives an Application Programming Interface (API) calling request;
the extraction module is used for extracting a user identifier, an API identifier and an API set identifier carried in the API calling request, wherein each API set identifier corresponds to a pre-divided API set, and each API set at least comprises one API;
the processing module is used for allowing the API corresponding to the API identification to be called when the fact that the API set identification carried in the API calling request has a corresponding relation with the user identification is determined, and the API set corresponding to the API set identification carried in the API calling request comprises the API corresponding to the API identification; and refusing to call the API corresponding to the API identification when determining that the API set identification carried in the API call request does not have a corresponding relationship with the user identification or the API set corresponding to the API set identification carried in the API call request does not include the API corresponding to the API identification.
The embodiment of the application adopts at least one technical scheme which can achieve the following beneficial effects:
the method comprises the steps of dividing the API on the open platform into a plurality of API sets, establishing a corresponding relation between each API set identification and the user identification of the third-party application, greatly simplifying the corresponding relation stored on the open platform because the number of the API sets is far smaller than that of the API, and judging whether the API set where the API to be called is located corresponds to the user identification by the open platform when the third-party application initiates an API calling request, so that the data volume needing to be processed by the server is greatly reduced, and the pressure of the server is further reduced.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
fig. 1 is a flowchart of a method for calling an application programming interface according to an embodiment of the present disclosure;
FIG. 2 is a schematic diagram of a calling device of an application programming interface according to an embodiment of the present disclosure;
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The technical solutions provided by the embodiments of the present application are described in detail below with reference to the accompanying drawings.
Fig. 1 is a flowchart of a method for calling an application programming interface according to an embodiment of the present application, including the following steps:
s101: an Application Programming Interface (API) call request is received.
In the embodiment of the present application, the API call request may be received by a server of the open platform, or may be received by an operating system (e.g., a Windows operating system, an IOS operating system, etc.), and all the functional units capable of providing the open API may be implementation subjects of the technical solution of the present application, which is not limited in this application. For convenience of description, the steps in the embodiments of the present application take an open platform as an example.
In this embodiment of the present application, the application requesting to call the API provided by the open platform may be a third-party web application, a third-party client application, or other applications that can be programmed by using the API to implement the function, which is not limited in this application.
S102: and extracting a user identifier, an API identifier and an API set identifier carried in the API call request, wherein each API set identifier corresponds to a pre-divided API set, and each API set at least comprises one API.
In this embodiment, the third-party application may send, to the open platform, an API call request carrying the user identifier, the API identifier, and the API set identifier according to the function to be implemented by the third-party application. The user identifier may be a user identifier obtained by registering a third-party application on an open platform in advance, or may be address information of the third-party application. Specifically, when the third-party application is a WEB application, the URL address of the WEB application may be used as the user identifier of the WEB application, and when the third-party application is a client application, the IP address of the client application may be used as the user identifier of the client application, and the user identifier is only required to uniquely identify the third-party application, which is not limited in this application.
In this embodiment of the application, the API identifier may be a storage address of the API requested to be called by the third party application in the open platform server, or may also be a number of the API requested to be called by the third party application on the open platform, and the API identifier only needs to uniquely identify the API, which is not limited in this application.
In the embodiment of the application, all or part of the APIs on the open platform may be divided into a plurality of API sets, each API set includes at least one API, and an API set identifier may be allocated to each API set. The APIs with similar functions may be divided into an API set, and the APIs that realize a certain complete function after combination may also be divided into an API set.
In this embodiment of the present application, each API set may be regarded as an application service product, and a developer of a third-party application may apply to the open platform, as needed, a permission granted to a certain API set, and once the third-party application is granted the permission to call the certain API set, the third-party application may call all APIs in the API set. Specifically, the third-party application may contract with the development platform, and agree that the third-party application has a call authority for a specified API set or API sets, and the open platform establishes, according to the contract relationship, a correspondence between the user identifier of the third-party application and the API set identifiers of the API sets contracted with the third-party application.
In addition, there may be an intersection or no intersection between API sets.
S103: and judging whether the API set identifier carried in the API calling request has a corresponding relation with the user identifier, if so, executing the step S104, otherwise, executing the step S106.
S104: and judging whether the API set corresponding to the API set identifier carried in the API call request comprises the API corresponding to the API identifier, if so, executing the step S105, otherwise, executing the step S106.
S105: and allowing to call the API corresponding to the API identification.
S106: and refusing to call the API corresponding to the API identification.
In the embodiment of the application, when determining that the API set identifier carried in the API call request has a corresponding relationship with the user identifier and the API set corresponding to the API set identifier carried in the API call request includes the API corresponding to the API identifier, allowing the API corresponding to the API identifier to be called; and refusing to call the API corresponding to the API identification when determining that the API set identification carried in the API call request does not have a corresponding relationship with the user identification or the API set corresponding to the API set identification carried in the API call request does not include the API corresponding to the API identification.
That is, the open platform needs to verify whether the third-party application signs the API set corresponding to the API set identifier notified by the third-party application, and also needs to verify whether the API set corresponding to the API set identifier notified by the third-party application contains the API to be called, and when both verifications pass, the open platform is allowed to call the API, and when at least one verification fails, the open platform directly rejects the API call. Wherein, the execution order of the two verifications is not limited.
Further, before step S105 is executed, that is, before the API corresponding to the API identifier is allowed to be called, it may be determined in advance whether the corresponding relationship between the API set identifier carried in the API call request and the user identifier is within the validity period, if the corresponding relationship is within the validity period, the API corresponding to the API identifier is allowed to be called, and if the corresponding relationship is not within the validity period, the API corresponding to the API identifier is refused to be called.
Specifically, before step S104 is executed, that is, before it is determined whether an API set corresponding to an API set identifier carried in the API call request includes an API corresponding to the API identifier, it is determined whether a corresponding relationship between the API set identifier carried in the API call request and the user identifier is within a validity period, or when step S103 is executed, that is, it is determined whether an API set identifier carried in the API call request and the user identifier have a corresponding relationship, and it is additionally determined whether a corresponding relationship between the API set identifier carried in the API call request and the user identifier is within the validity period, or after step S104 is executed, it is determined whether a corresponding relationship between the API set identifier carried in the API call request and the user identifier is within the validity period. Allowing a third-party application to call the API as long as the two verifications are passed and the corresponding relation between the API set containing the API to be called and the user identification is still within the validity period; and refusing the third-party application to call the API as long as the at least one verification is not passed or the corresponding relation between the API set containing the API to be called and the user identification is not within the validity period.
It should be noted that the validity period may be a validity period that the open platform and the third-party application developer have agreed in advance for the signed API set, for example, the third-party application developer may sign with the API set including the API1, the API5, and the API30 on the open platform as required, and the subscription validity period is 2015, 12, month 1, day 0 to 2016, 6, month 1, day 0.
Further, in the embodiment of the present application, since the open platform pre-stores the corresponding relationship between the user identifier and the API set identifier, when the third-party application initiates the API call request, the API call request may not carry the API set identifier, but only carry the user identifier and the API identifier. Therefore, the open platform determines the API set identifier corresponding to the user identifier according to the user identifier, then judges whether the API set corresponding to the determined API set identifier comprises the API corresponding to the API identifier, if so, the call is allowed, otherwise, the call is rejected. Similarly, before allowing the call, it may also be determined in advance whether the correspondence between the API set identifier carried in the API call request and the user identifier is within the validity period, which is not described herein again.
By the method shown in fig. 1, all APIs stored on the open platform are divided into at least one API set, an identifier is allocated to each API set and a user identifier is allocated to each third-party application, and a corresponding relationship between each API set identifier and each user identifier is established, so that when an API call request is received, the open platform only needs to determine whether the user identifier and the API set identifier carried in the API call request have a corresponding relationship and whether the API set corresponding to the API set identifier carried in the API call request includes an API requested to be called. Because the number of the API sets is far less than that of the APIs, the corresponding relation required to be processed by the open platform server is greatly simplified. The scheme obviously reduces the data volume processed by the open platform server and lightens the pressure of the server.
Based on the calling method of the application programming interface shown in fig. 1, an embodiment of the present application further provides a calling device of the application programming interface, as shown in fig. 2.
Fig. 2 is a schematic diagram of another calling device of an application programming interface according to an embodiment of the present application, including:
a receiving module 201, which receives an application programming interface API call request;
the extracting module 202 is configured to extract a user identifier, an API identifier, and an API set identifier carried in the API call request, where each API set identifier corresponds to a pre-divided API set, and each API set includes at least one API;
the processing module 203 allows to call the API corresponding to the API identifier when it is determined that the API set identifier carried in the API call request has a corresponding relationship with the user identifier and the API set corresponding to the API set identifier carried in the API call request includes the API corresponding to the API identifier; and refusing to call the API corresponding to the API identification when determining that the API set identification carried in the API call request does not have a corresponding relationship with the user identification or the API set corresponding to the API set identification carried in the API call request does not include the API corresponding to the API identification.
Wherein, there is an intersection or no intersection between different API sets.
Furthermore, the apparatus further comprises: the aging control module 204 determines that the correspondence between the API set identifier carried in the API call request and the user identifier is within the validity period before the processing module 203 allows calling the API corresponding to the API identifier.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (6)
1. A calling method of an application programming interface is characterized by comprising the following steps:
receiving an Application Programming Interface (API) calling request;
extracting user identifiers, API identifiers and API set identifiers carried in the API call request, wherein each API set identifier corresponds to a pre-divided API set, and each API set at least comprises one API;
judging whether an API set identifier carried in the API calling request has a corresponding relation with the user identifier;
when the API set identification carried in the API call request has a corresponding relation with the user identification, judging whether the API set corresponding to the API set identification carried in the API call request comprises the API corresponding to the API identification; when the API set corresponding to the API set identifier carried in the API call request comprises the API corresponding to the API identifier, allowing to call the API corresponding to the API identifier; when the API set corresponding to the API set identifier carried in the API call request does not include the API corresponding to the API identifier, refusing to call the API corresponding to the API identifier;
and when the API set identification carried in the API calling request does not have a corresponding relation with the user identification, refusing to call the API corresponding to the API identification.
2. The method of claim 1, wherein there is an intersection or no intersection between different API sets.
3. The method of claim 1 or 2, wherein before allowing the calling of the API to identify the corresponding API, the method further comprises:
and determining that the corresponding relation between the API set identification carried in the API call request and the user identification is within the validity period.
4. An apparatus for invoking an application programming interface, comprising:
the receiving module receives an Application Programming Interface (API) calling request;
the extraction module is used for extracting a user identifier, an API identifier and an API set identifier carried in the API calling request, wherein each API set identifier corresponds to a pre-divided API set, and each API set at least comprises one API;
the processing module is used for judging whether the API set identification carried in the API calling request has a corresponding relation with the user identification;
when the API set identification carried in the API call request has a corresponding relation with the user identification, judging whether the API set corresponding to the API set identification carried in the API call request comprises the API corresponding to the API identification; when the API set corresponding to the API set identifier carried in the API call request comprises the API corresponding to the API identifier, allowing to call the API corresponding to the API identifier; when the API set corresponding to the API set identifier carried in the API call request does not include the API corresponding to the API identifier, refusing to call the API corresponding to the API identifier;
and when the API set identification carried in the API calling request does not have a corresponding relation with the user identification, refusing to call the API corresponding to the API identification.
5. The apparatus of claim 4, wherein there is an intersection or no intersection between different API sets.
6. The apparatus of claim 4 or 5, further comprising:
and the time efficiency control module is used for determining that the corresponding relation between the API set identifier carried in the API calling request and the user identifier is within the validity period before the processing module allows calling of the API corresponding to the API identifier.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610529818.1A CN106873958B (en) | 2016-07-06 | 2016-07-06 | Calling method and device of application programming interface |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610529818.1A CN106873958B (en) | 2016-07-06 | 2016-07-06 | Calling method and device of application programming interface |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106873958A CN106873958A (en) | 2017-06-20 |
| CN106873958B true CN106873958B (en) | 2020-06-23 |
Family
ID=59239365
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610529818.1A Active CN106873958B (en) | 2016-07-06 | 2016-07-06 | Calling method and device of application programming interface |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106873958B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109829287A (en) * | 2018-11-20 | 2019-05-31 | 新疆福禄网络科技有限公司 | Api interface permission access method, equipment, storage medium and device |
| CN111416793B (en) * | 2019-01-08 | 2022-05-24 | 杭州海康威视数字技术股份有限公司 | Permission control method based on open platform and embedded equipment |
| CN112559463B (en) * | 2020-12-18 | 2023-08-25 | 杭州数梦工场科技有限公司 | Compressed file processing method and device |
| CN112612517B (en) * | 2020-12-18 | 2024-04-05 | 深圳市思为软件技术有限公司 | Data acquisition method and related equipment |
| CN112560016A (en) * | 2020-12-23 | 2021-03-26 | 平安银行股份有限公司 | Service request management method and device, computer equipment and readable storage medium |
| CN113656025A (en) * | 2021-08-05 | 2021-11-16 | 北京趣拿软件科技有限公司 | API processing method and device |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103593238A (en) * | 2012-08-16 | 2014-02-19 | 腾讯科技（深圳）有限公司 | Method and device for controlling invocation of application programming interfaces |
| CN103995889A (en) * | 2014-06-03 | 2014-08-20 | 广东欧珀移动通信有限公司 | Method and device for classifying pictures |
| CN104301331A (en) * | 2014-10-31 | 2015-01-21 | 北京思特奇信息技术股份有限公司 | Service interface permissions validation method and device |
-
2016
- 2016-07-06 CN CN201610529818.1A patent/CN106873958B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103593238A (en) * | 2012-08-16 | 2014-02-19 | 腾讯科技（深圳）有限公司 | Method and device for controlling invocation of application programming interfaces |
| CN103995889A (en) * | 2014-06-03 | 2014-08-20 | 广东欧珀移动通信有限公司 | Method and device for classifying pictures |
| CN104301331A (en) * | 2014-10-31 | 2015-01-21 | 北京思特奇信息技术股份有限公司 | Service interface permissions validation method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106873958A (en) | 2017-06-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106873958B (en) | Calling method and device of application programming interface | |
| CN109033774B (en) | Method and device for acquiring and feeding back user resources and electronic equipment | |
| CN112564916A (en) | Access client authentication system applied to micro-service architecture | |
| CN113079200A (en) | Data processing method, device and system | |
| CN109086596B (en) | Authentication method, device and system for application program | |
| CN107040560B (en) | Service processing method and device based on service platform | |
| CN106951795B (en) | Application data access isolation method and device | |
| CN112434348B (en) | Data verification processing method, device and equipment | |
| RU2734027C2 (en) | Method and device for preventing an attack on a server | |
| CN110909373A (en) | Access control method, device, system and storage medium | |
| CN113821817B (en) | Data processing method, device, equipment and system based on block chain | |
| CN114091099A (en) | Authority hierarchical control method, equipment and storage medium for business system | |
| CN115082185A (en) | Method, device, equipment and medium for channel fast access loan service system | |
| CN106982193B (en) | Method and device for preventing batch registration | |
| CN114065157A (en) | Page scheduling authentication method, equipment and medium in multi-tenant mode | |
| CN107528822B (en) | Service execution method and device | |
| CN111131474A (en) | Method, device and medium for managing user protocol based on block chain | |
| CN112734349A (en) | Interface generation method, data calling method, device and electronic equipment | |
| CN112866265B (en) | CSRF attack protection method and device | |
| CN115511595A (en) | Service execution method and device based on block chain | |
| CN112100610B (en) | Processing method, device and equipment for login and user login related services | |
| CN115827589A (en) | Authority verification method and device, electronic equipment and storage medium | |
| CN110806935B (en) | Application program construction method, device and system | |
| CN111444483A (en) | Authentication method, device and equipment | |
| CN109299117B (en) | Data request processing method and device, storage medium and processor |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20201014 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee after: Innovative advanced technology Co.,Ltd. Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20201014 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee after: Advanced innovation technology Co.,Ltd. Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Patentee before: Alibaba Group Holding Ltd. |
|
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20240228 Address after: 128 Meizhi Road, Guohao Times City # 20-01, Singapore 189773 Patentee after: Advanced Nova Technology (Singapore) Holdings Ltd. Country or region after: Singapore Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee before: Innovative advanced technology Co.,Ltd. Country or region before: Cayman Islands |