US 11,677,855 B2
Managing application programming interface (API) path trends
Derric Stephen Gilling, San Francisco, CA (US); Xingheng Timothy Wang, San Francisco, CA (US); and Devendra Kumar Modium, San Francisco, CA (US)
Assigned to Moesif, Inc., San Francisco, CA (US)
Filed by Moesif, Inc., San Francisco, CA (US)
Filed on Aug. 6, 2020, as Appl. No. 16/986,636.
Claims priority of provisional application 62/883,379, filed on Aug. 6, 2019.
Prior Publication US 2021/0044672 A1, Feb. 11, 2021
Int. Cl. H04L 67/60 (2022.01); H04L 69/22 (2022.01); H04L 67/306 (2022.01); G06F 9/54 (2006.01); H04L 67/133 (2022.01); H04L 67/50 (2022.01)
CPC H04L 67/60 (2022.05) [G06F 9/541 (2013.01); H04L 67/133 (2022.05); H04L 67/306 (2013.01); H04L 67/535 (2022.05); H04L 69/22 (2013.01)] 18 Claims
OG exemplary drawing
 
1. A method comprising:
obtaining application programming interface (API) request information associated with API requests to an API provider from a plurality of users during a first period, wherein the API request information comprises API function identifiers associated with the API requests;
identifying sequences of API requests from the plurality of users based on the API request information;
identifying a rate of use for a sequence in the sequences of API requests based on the API request information;
obtaining second API request information associated with second API requests to the API provider from the plurality of users during a second period;
identifying second sequences of API requests from the plurality of users based on the second API request information;
identifying a second rate of use for the sequence in the second sequences;
identifying an API path trend based on a difference between the first rate of use and the second rate of use satisfying one or more criteria; and
generating a summary based on the identified API path trend.