Systems and methods to identify breaking application program interface changes

A method for managing application programming interfaces (API) comprising:

• sending a first call to a first node-testing model associated with a first API;
• receiving from the first node-testing model, a first model output based on the first call, the first model output comprising a first model result and a first model-result category;
• receiving API call data associated with a plurality of APIs;
• training a routing model to identify routing pathways between API nodes using the API call data;
• sending the first model result to the routing model;
• after sending the first model result, receiving, from the routing model, information identifying a second node-testing model associated with a second API;
• sending a second call to the second node-testing model, the second call being based on the first model result;
• receiving, from the second node-testing model, a second model output based on the second call, the second model output comprising a second model result and a second model-result category;
• and
• performing at least one of:
• generating an updated first node-testing model based on the first node-testing model when the first model result category comprises a failure or an unknown result;
• generating an updated second node-testing model based on the second node-testing model when the second model result category comprises a failure or an unknown result;
• generating, by a first translation model, an updated first call when the first model result category comprises a failure;
• or
• generating, by a second translation model, an updated second call when the second model result category comprises a failure.

A system for managing application programming interfaces (APIs), comprising:

• one or more memory units storing instructions;
• and
• one or more processors that execute the instructions to perform operations comprising:
• receiving API call data associated with a plurality of APIs;
• generating a plurality of node-testing models associated with the APIs;
• sending a first call to a first one of the node-testing models;
• receiving from the first node-testing model, a first model output based on the first call, the first model output comprising a first model result and a first model-result category;
• receiving API call data associated with a plurality of APIs;
• training a routing model to identify routing pathways between API nodes using the API call data;
• sending the first model result to the routing model;
• after sending the first model result, receiving, from the routing model, information identifying a second node-testing model associated with a second API;
• and
• performing at least one of:
• sending a second call to the second node-testing model, the second call being based on the first model result;
• generating an updated first node-testing model based on the first node-testing model when the first model result category comprises at least one of a failure or an unknown result;
• or
• generating, by a translation model, an updated first call when the first model result category comprises a failure.