US 12,353,875 B2
Auto-documentation for application program interfaces based on network requests and responses
Marco Palladino, San Francisco, CA (US); and Augusto Marietti, San Francisco, CA (US)
Assigned to KONG INC., San Francisco, CA (US)
Filed by KONG INC., San Francisco, CA (US)
Filed on Nov. 2, 2023, as Appl. No. 18/500,372.
Application 18/500,372 is a continuation of application No. 18/154,682, filed on Jan. 13, 2023, granted, now 11,838,355.
Application 18/154,682 is a continuation of application No. 16/933,287, filed on Jul. 20, 2020, granted, now 11,582,291, issued on Feb. 14, 2023.
Application 16/933,287 is a continuation in part of application No. 16/714,662, filed on Dec. 13, 2019, granted, now 11,171,842, issued on Nov. 9, 2021.
Application 16/933,287 is a continuation in part of application No. 16/254,788, filed on Jan. 23, 2019, abandoned.
Application 16/714,662 is a continuation of application No. 15/974,532, filed on May 8, 2018, granted, now 10,225,330, issued on Mar. 5, 2019.
Application 15/974,532 is a continuation in part of application No. 15/899,529, filed on Feb. 20, 2018, granted, now 10,097,624, issued on Oct. 9, 2018.
Application 15/899,529 is a continuation of application No. 15/662,539, filed on Jul. 28, 2017, granted, now 9,936,005, issued on Apr. 3, 2018.
Claims priority of provisional application 62/896,412, filed on Sep. 5, 2019.
Prior Publication US 2024/0064195 A1, Feb. 22, 2024
Int. Cl. G06F 8/73 (2018.01); H04L 67/10 (2022.01); H04L 67/1004 (2022.01); H04L 67/01 (2022.01); H04L 67/02 (2022.01); H04L 67/563 (2022.01); H04L 67/568 (2022.01)
CPC G06F 8/73 (2013.01) [H04L 67/10 (2013.01); H04L 67/1004 (2013.01); H04L 67/01 (2022.05); H04L 67/02 (2013.01); H04L 67/563 (2022.05); H04L 67/568 (2022.05)] 22 Claims
OG exemplary drawing
 
1. A method for managing Application Programming Interfaces (APIs) in a microservices architecture, the method comprising:
communicatively coupling a control plane to a plurality of APIs organized into a microservices application architecture via data plane proxies;
receiving an incoming proxied request generated by a first API of the plurality of APIs and intended for a second API of the plurality of APIs, the proxied request relayed to the control plane via a first data plane proxy associated with the first API;
receiving a response from the second API;
inspecting, by an artificial intelligence model, at least one of:
a parameter of the proxied request or a parameter of the response from the second API,
a history of parameters received by the first API or the second API, or
a history of responses returned by requests generated by the first API,
wherein output of the artificial intelligence model indicates an expected operation of the first API or the second API based on the inspection of at least one of the parameter of the proxied request or the parameter of the response from the second API, the history of parameters received by the first or second API, or the history of responses returned by requests generated by the first API; and
executing an auto-documentation plugin, wherein the auto-documentation plugin is configured to generate documentation based on the output of the artificial intelligence model.