# US 12,008,366 B2 · Correlating usage to issues in application programming interfaces > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,008,366 B2 - Document ID: US12008366B2 - Status: Granted - Kind: B2 - Application number: 17/805,233 - Filed: 2022-06-03 - Published: 2023-12-07 - Granted: 2024-06-11 - Earliest claimed: 2022-06-03 - Assignees: International Business Machines Corporation - Applicants: International Business Machines Corporation - Inventors: Ravi Chandra Chamarthy; Prateek Goyal; Manish Anand Bhide; Madhavi Katari - Web page: https://patentgrep.com/patent/US12008366B2 ## CPC - G06F 8/77: Software metrics - G06F 8/36: Software reuse - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Early indications of application programming interface (API) usage are identified by correlation to particular issues with the API including singular and mutual consistency, completeness, accuracy, and staleness. Analysis of API input and output along with data type and formatting information facilitates identification of the API issues. Establishing a correlation between API usage and issues supports early detection of potential usage reduction on a case-by-case level. Corrective action to resolve identified issues may be performed in a timely manner to maintain usage levels. ## Claims ### Claim 1 A computer-implemented method for correlating application programming interface (API) usage to issues in APIs, the method comprising: identifying field characteristics of API input/output (I/O) data generated during operation of an API; validating the I/O data based on a set of issue criteria; identifying a set of issues for a first user, the set of issues identified in the set of issue criteria; establishing a degree of correlation of an identified issue to API usage reduction; and responsive to the degree of correlation meeting a threshold degree of correlation, taking a retention action corresponding to the threshold degree. ### Claim 2 (depends on 1) The method of claim 1, further comprising: monitoring usage of the API by the first user; wherein: the identified issue is a combination of issues in the identified set of issues. ### Claim 3 (depends on 1) The method of claim 1, further comprising: determining an average staleness of a selected field of the API I/O data; and comparing the average staleness to a staleness value of the selected field for the first user; wherein: the identified issue is staleness. ### Claim 4 (depends on 1) The method of claim 1, wherein: the threshold degree of correlation is one threshold range of a plurality of threshold ranges; and the retention action corresponds to the threshold range in which the degree of correlation is found. ### Claim 5 (depends on 1) The method of claim 1, wherein the issue criteria include mutual field consistency and data completeness. ### Claim 6 (depends on 1) The method of claim 1, wherein the field characteristics include a number of digits of a first field and a pattern of digits and characters of a second field. ### Claim 7 (depends on 1) The method of claim 1, further comprising: collecting the API I/O data during operation of the API. ### Claim 8 (depends on 1) The method of claim 1, wherein the retention action is to identify from an offer service, a special offer to be directed to the first user. ### Claim 9 A computer system for correlating application programming interface (API) usage to issues in APIs, the computer system comprising: a processor set; and a computer readable storage medium; wherein: the processor set is structured, located, connected, and/or programmed to run program instructions stored on the computer readable storage medium; and the program instructions which, when executed by the processor set, cause the processor set to perform a method comprising: identifying field characteristics of API input/output (I/O) data generated during operation of an API; validating the I/O data based on a set of issue criteria; identifying a set of issues for a first user, the set of issues identified in the set of issue criteria; establishing a degree of correlation of an identified issue to API usage reduction; and responsive to the degree of correlation meeting a threshold degree of correlation, taking a retention action corresponding to the threshold degree. ### Claim 10 (depends on 9) The computer system of claim 9, where the program instructions further cause the processor set to perform: monitoring usage of the API by the first user; wherein: the identified issue is a combination of issues in the identified set of issues. ### Claim 11 (depends on 9) The computer system of claim 9, where the program instructions further cause the processor set to perform: determining an average staleness of a selected field of the API I/O data; and comparing the average staleness to a staleness value of the selected field for the first user; wherein: the identified issue is staleness. ### Claim 12 (depends on 9) The computer system of claim 9, wherein: the threshold degree of correlation is one threshold range of a plurality of threshold ranges; and the retention action corresponds to the threshold range in which the degree of correlation is found. ### Claim 13 (depends on 9) The computer system of claim 9, wherein the issue criteria include mutual field consistency and data completeness. ### Claim 14 (depends on 9) The computer system of claim 9, wherein the field characteristics include a number of digits of a first field and a pattern of digits and characters of a second field. ### Claim 15 (depends on 9) The computer system of claim 9, where the program instructions further cause the processor set to perform: collecting the API I/O data during operation of the API. ### Claim 16 A computer program product comprising a computer-readable storage medium having a set of instructions stored therein which, when executed by a processor, causes the processor to perform a method comprising: identifying field characteristics of application programming interface (API) input/output (I/O) data generated during operation of an API; validating the I/O data based on a set of issue criteria; identifying a set of issues for a first user, the set of issues identified in the set of issue criteria; establishing a degree of correlation of an identified issue to API usage reduction; and responsive to the degree of correlation meeting a threshold degree of correlation, taking a retention action corresponding to the threshold degree. ### Claim 17 (depends on 16) The computer program product of claim 16, wherein the set of instructions further cause the processor to perform: monitoring usage of the API by the first user; wherein: the identified issue is a combination of issues in the identified set of issues. ### Claim 18 (depends on 16) The computer program product of claim 16, wherein the set of instructions further cause the processor to perform: determining an average staleness of a selected field of the API I/O data; and comparing the average staleness to a staleness value of the selected field for the first user; wherein: the identified issue is staleness. ### Claim 19 (depends on 16) The computer program product of claim 16, wherein: the threshold degree of correlation is one threshold range of a plurality of threshold ranges; and the retention action corresponds to the threshold range in which the degree of correlation is found. ### Claim 20 (depends on 16) The computer program product of claim 16, wherein the issue criteria include mutual field consistency and data completeness.