Systems and methods for managing application programming interface information

Patent metadata

Field	Value
Publication number	US-11755386-B2
Application number	US-202117174901-A
Country	US
Kind code	B2
Filing date	Feb 12, 2021
Priority date	Mar 11, 2019
Publication date	Sep 12, 2023
Grant date	Sep 12, 2023

Abstract

Computerized systems and methods for managing API information. An exemplary method includes receiving an input from a user device associated with a first computer system, the input not including identity of a second computer system. The method includes determining a target API based on the input, the target API being the second computer system's API. The method also includes determining whether a user of the user device has access to the target API. The method includes retrieving documentation of the target API from an API database if it is determined that the user has access to the target API. The method includes providing the user device with the retrieved documentation.

First claim

What is claimed is:

1. An application programming interface (API) management system for managing API information, the API management system comprising:
at least one processor;
an API database storing data associated with APIs; and
at least one memory containing instructions that, when executed by the at least one processor, cause the processor to perform operations comprising:
receiving, by an interface of the API management system, an API registration request and API data associated with an API, wherein the API data comprises access information, and wherein the access information identifies a group of entities permitted to access the API;
generating documentation associated with the API based on the API registration request;
generating, by the API management system, a rule set for generating code using the API based on the API registration request, wherein the API management system uses the rule set to generate code associated with the API when a user from among the group of entities is connected to the API; and
storing, by the API management system, the generated documentation and the API data in the API database, wherein the API management system:
connects a user device to the API data in response to a connection request; and
generates base source code and supplemental source code by determining and selecting most used parts of the API data, wherein the most used parts of the API data is determined based on a review and assignment of weighted coefficient to related records wherein the API data was previously used.

2. The API management system of claim 1 , wherein the API registration request and API data are received from a user device, wherein the user device uses the API.

3. The API management system of claim 1 , wherein the API registration request and API data are received from a user device in a fulfillment optimization system for computing a promised delivery date for a product.

4. The API management system of claim 1 , wherein the API data comprises at least one of: index information, identification information, permission level authorization information, introduction notes, rules, development and debugging notes, or a record of previous use of the API.

5. The API management system of claim 1 , wherein the group of entities identified by the access information comprises at least one of: any user, any API, or any computer system.

6. The API management system of claim 1 , wherein the group of entities identified by the access information comprises at least one of: a particular group of users, APIs, or computer systems given access; a particular group of users, APIs, or computer systems not given access; or an access criteria of receiving a connection request to connect to the API.

7. The API management system of claim 1 , wherein the documentation is generated based on the API data.

8. The API management system of claim 7 , wherein the operations further comprises:
receiving an input from a user device;
identifying the API as a target API of the input;
in response to the input, performing at least one of: retrieving the documentation or generating the base source code associated with the target API; and
providing the user device with the at least one of the documentation or the generated base source code.

9. The API management system of claim 8 , wherein the operations further comprises:
determining that the supplemental source code associated with at least one API different from the target API is responsive to the input; and
generating the supplemental source code associated with the at least one API different from the target API, wherein the supplemental source code is added to the generated base source code.

10. The API management system of claim 8 , wherein:
the input includes at least one keyword; and
the API is identified as the target API based on the at least one keyword.

11. The API management system of claim 8 , wherein the API is identified as the target API based on a record of use of the API.

12. The API management system of claim 8 , wherein the API is identified as the target API based on at least one of: a search history associated with the user device, selection history associated with the user device, or using history associated with the user device.

13. The API management system of claim 8 , wherein the operations further comprises:
providing a list of APIs to the user device, the list being based on the input and including the API;
receiving a selection of the API from the user device, wherein the API is identified as the target API based on the received selection.

14. The API management system of claim 13 , wherein the list of APIs is further based on popularities associated with the APIs.

15. The API management system of claim 1 , wherein the operations further comprises receiving an API update request and additional API data.

16. The API management system of claim 15 , wherein the operations further comprises updating at least the rule set or the documentation.

17. The API management system of claim 16 , wherein the operations further comprises sending a notification to at least one computer system.

18. The API management system of claim 17 , wherein the at least one computer system was identified as part of the group of entities permitted to access the API.

19. A method for managing application programming interface (API) information comprising:
receiving an API registration request and API data associated with an API, wherein the API data comprises access information, and wherein the access information identifies a group of entities permitted to access the API;
generating documentation associated with the API based on the API registration request;
generating a rule set for generating code using the API based on the API registration request, wherein the rule set is used to generate code associated with the API when a user from among the group of entities is connected to the API; and
storing the generated documentation and the API data in an API database, wherein the API database:
connects a user device to the API data in response to a connection request; and
generates base source code and supplemental source code by determining and selecting most used parts of the API data, wherein the most used parts of the API data is determined based on a review and assignment of weighted coefficient to related records wherein the API data was previously used.

20. An application programming interface (API) management system for managing API information, the API management system comprising:
at least one processor;
an API database storing data associated with APIs; and
at least one memory containing instructions that, when executed by the at least one processor, cause the processor to perform operations comprising:
receiving, by an interface of the API management system, an API registration request and API data associated with an API, wherein the API data comprises access information, and wherein the access information identifies a group of entities permitted to access the API;
generating documentation associated with the API based on the API registration request;
generating, by the API management system, a rule set for generating code using the API based on the API registration request, wherein the API management system uses the rule set to generate code associated with the API when a user from among the group of entities is connected to the API;
storing, by the API management system, the generated documentation and the API data in the API database, wherein

Assignees

• Coupang Corp

Inventors

• Park Young Jin
• Yoon Yong Hyun
• Yang Won Suk

Classifications

• G06F16/25 Primary

  Integrating or interfacing systems involving database management systems · CPC title

• G06F8/36 Primary

  Software reuse · CPC title

• G06F8/38 Primary

  for implementing user interfaces · CPC title

• G06F9/54 Primary

  Interprogram communication · CPC title

• G06F9/4482

  Procedural · CPC title