# US 2021/0240549 A1 · Systems and methods for managing application programming interface information > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2021/0240549 A1 - Document ID: US20210240549A1 - Status: Published application - Kind: A1 - Application number: 17/174,901 - Filed: 2021-02-12 - Published: 2021-08-05 - Earliest claimed: 2019-03-11 - Assignees: Coupang Corp. - Applicants: Coupang Corp. - Inventors: Young Jin Park; Yong Hyun Yoon; Won Suk Yang - Web page: https://patentgrep.com/patent/US20210240549A1 ## CPC - G06F 9/54: Interprogram communication - G06F 8/35: model driven - G06F 8/36: Software reuse - G06F 8/43: {Checking; Contextual analysis} - G06F 16/9035: Filtering based on additional data, e.g. user or group profiles - G06F 16/93: Document management systems - G06F 8/60: Software deployment - G06F 8/73: Program documentation - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## 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. ## Claims ### Claim at position 1 1-20. (canceled) ### Claim 21 A computer-implemented system for managing application programming interface (API) information, the system comprising: at least one processor; an API database storing data associated with APIs, each API being associated with at least one computer system; and at least one memory containing instructions that, when executed by the at least one processor, cause the processor to perform operations comprising: receiving an API registration request and API data associated with an API, the API data comprising access information, the access information identifying 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, the rule set being configured for use by the system to generated 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 the API database, wherein the system is configured to connect a user device to the API data in response to a request. ### Claim 22 (depends on 21) The computer-implemented system of claim 21, wherein the API registration request and API data are received from a user device configured to use the API. ### Claim 23 (depends on 21) The computer-implemented system of claim 21, wherein the API registration request and API data are received from a user device in a fulfillment optimization system configured to compute a promised delivery date for a product. ### Claim 24 (depends on 21) The computer-implemented system of claim 21, 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. ### Claim 25 (depends on 21) The computer-implemented system of claim 21, wherein the group of entities identified by the access information comprises at least one of: any user, any API, or any computer system. ### Claim 26 (depends on 21) The computer-implemented system of claim 21, 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 request to connect to the API. ### Claim 27 (depends on 21) The computer-implemented system of claim 21, the documentation is generated based on the API data. ### Claim 28 (depends on 27) The computer-implemented system of claim 27, the operations further comprising: 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 source code associated with the target API; and providing the user device with the at least one of the documentation or the generated source code. ### Claim 29 (depends on 28) The computer-implemented system of claim 28, the operations further comprising: determining that a supplemental source code associated with at least one API different from the target API is responsive to the input; generating the supplemental source code associated with the at least one API different from the target API, the supplemental source code being added to the generated source code. ### Claim 30 (depends on 28) The computer-implemented system of claim 28, wherein: the input includes at least one keyword; and the API is identified as the target API based on the at least one keyword. ### Claim 31 (depends on 28) The computer-implemented system of claim 28, wherein the API is identified as the target API based on a record of use of the API. ### Claim 32 (depends on 28) The computer-implemented system of claim 28, 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. ### Claim 33 (depends on 28) The computer-implemented system of claim 28, the operations further comprising: 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. ### Claim 34 (depends on 33) The computer-implemented system of claim 33, wherein the list of APIs is further based on popularities associated with the APIs. ### Claim 35 (depends on 21) The computer-implemented system of claim 21, wherein the operations further comprising receiving an API update request and additional API data ### Claim 36 (depends on 35) The computer-implemented system of claim 35, wherein the operations further comprising updating at least the rule set or the documentation. ### Claim 37 (depends on 36) The computer-implemented system of claim 36, the operations further comprising sending a notification to at least one computer system. ### Claim 38 (depends on 37) The computer-implemented system of claim 37, wherein the at least one computer system was identified as part of the group of entities permitted to access the API. ### Claim 39 A method for managing application programming interface (API) information comprising: receiving an API registration request and API data associated with an API, the API data comprising access information, the access information identifying 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, the rule set being configured for use by the system to generated 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 is configured to connect a user device to the API data in response to a request. ### Claim 40 A computer-implemented system for managing application programming interface (API) information, the system comprising: at least one processor; an API database storing data associated with APIs, each API being associated with at least one computer system; and at least one memory containing instructions that, when executed by the at least one processor, cause the processor to perform operations comprising: receiving an API registration request and API data associated with an API, the API data comprising access information, the access information identifying 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, the rule set being configured for use by the system to generated code associated with the API when a user from among the group of entities is connected to the API; storing the generated documentation and the API data in the API database, wherein the system is configured to connect a user device to the API data in response to a request; receiving an input from a user device; determining that the user device is authorized to access the API; based on determining that the user device is authorized to access the API, 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 source code associated with the target API; and providing the user device with the at least one of the documentation or the generated source code.