Systems and methods for vendor alerts from analyzed third party sources

1 . A method comprising:

establishing, by one or more processors of a first computing system, a connection between the first computing system and an application hosted on one or more servers of a second computing system, responsive to receiving a first application program interface (API) call at the first computing system;

retrieving, by the one or more processors, responsive to receiving a second API call at an API gateway circuit, a dataset comprising a list of entities from a data store maintained by the application, the list of entities associated with an account holder of an account with the application, wherein retrieving the dataset comprises:

determining, by the one or more processors, based on information in the second API call, at least one circuit of a plurality of circuits internal to the API gateway circuit configured to process the second API call;

routing, by the one or more processors via the API gateway circuit, the second API call to the at least one circuit; and

receiving, by the one or more processors via the at least one circuit, the dataset as API response data;

detecting, by the one or more processors, an event associated with an entity of the list of entities, based on the dataset received as the API response data and data from a third-party server;

generating, by the one or more processors, an alert corresponding to the event for rendering at a user interface corresponding to the first computing system; and

responsive to a user interaction with the alert at the user interface, executing, by the one or more processors using the at least one circuit, a transaction with the entity associated with the event.

2 . The method of claim 1 , wherein detecting the event comprises:

receiving, by the one or more processors, the data from the third-party server;

applying, by the one or more processors, the data to a machine learning model trained to normalize the data, to determine normalized data from the data; and

detecting, by the one or more processors, the event based on the normalized data from the machine learning model.

3 . The method of claim 2 , wherein the machine learning model is a first machine learning model, the method further comprising:

applying, by the one or more processors, the event to a second machine learning model trained to generate recommendations given one or more events as an input; and

determining, by the one or more processors, a recommendation for the event associated with the entity based on an output from the second machine learning model.

4 . The method of claim 3 , wherein the alert includes the recommendation determined for the event.

5 . The method of claim 2 , wherein the third-party server comprises a first third-party server, and wherein detecting the event based on the normalized data from the machine learning model comprises:

scraping, by the one or more processors, the data from the first third-party server to identify one or more identifiers of the entity included in the data;

generating, by the one or more processors, a query for a second third-party server using the one or more identifiers; and

verifying, by the one or more processors, the entity identified in the data from the first third-party server as matching the entity in the list of entities in the dataset base on a response to the query from the second third-party server.

6 . The method of claim 5 , wherein generating the alert is responsive to verifying the entity as matching the entity in the list of entities.

7 . The method of claim 5 , further comprising:

computing, by the one or more processors, a first score for the event and a second score for matching the entity identified in the data to the entity in the list of entities in the dataset, wherein the alert is generated responsive to the first score and the second score satisfying a threshold criteria.

8 . The method of claim 1 , wherein detecting the event comprises:

receiving, by one or more processors, content from a third party server including one or more identifiers of the entity and one or more metrics corresponding to the event;

normalizing, by the one or more processors, the one or more metrics;

determining, by the one or more processors, that the normalized one or more metrics satisfy a criterion for identifying the presence of the event;

computing, by the one or more processors, a match score based on the one or more identifiers being associated with the entity from the list of entities included in the dataset; and

detecting, by the one or more processors, the event associated with the entity responsive to the match score satisfying a threshold criteria and the normalized one or more metrics satisfying the criterion.

9 . The method of claim 8 , wherein generating the alert comprises:

applying, by the one or more processors, data corresponding to the event and one or more values from fields retrieved from an account with the second computing system to a machine learning model trained to generate recommendations for corresponding events; and

generating, by the one or more processors, the alert to include a recommendation corresponding to an alternative entity with respect to the entity.

10 . A system comprising:

one or more processors configured to:

establish a connection between a first computing system and an application hosted on one or more servers of a second computing system in response to receiving a first application program interface (API) call at the first computing system;

retrieve, responsive to receiving a second API call at an API gateway circuit, a dataset comprising a list of entities from a data store maintained by the application, the list of entities associated with an account holder of an account with the application, wherein retrieving the dataset comprises:

determine, based on information in the second API call, at least one circuit of a plurality of circuits internal to the API gateway circuit configured to process the second API call;

route, via the API gateway circuit, the second API call to the at least one circuit; and

receive, via the at least one circuit, the dataset as API response data;

detect an event associated with an entity of the list of entities, based on the dataset received as the API response data and data from a third-party server;

generate an alert corresponding to the event for rendering at a user interface corresponding to the first computing system; and

responsive to a user interaction with the alert at the user interface, execute, using the at least one circuit, a transaction with the entity associated with the event.

11 . The system of claim 10 , wherein to detect the event, the one or more processors are configured to:

receive the data from the third-party server;

apply the data to a machine learning model trained to normalize the data, to determine normalized data from the data; and

detect the event based on the normalized data from the machine learning model.

12 . The system of claim 11 , wherein the machine learning model is a first machine learning model, wherein the one or more processors are configured to:

apply the event to a second machine learning model trained to generate recommendations given one or more events as an input; and

determine a recommendation for the event associated with the entity based on an output from the second machine learning model.

13 . The system of claim 12 , wherein the alert includes the recommendation determined for the event.

14 . The system of claim 11 , wherein the third-party server comprises a first third-party server, and wherein detecting the event based on the normalized data from the machine learning model comprises:

scraping, by the one or more processors, the data from the first third-party server to identify one or more identifiers of the entity included in the data;

generating, by the one or more processors, a query for a second third-party server using the one or more identifiers; and

verifying, by the one or more processors, the entity identified in the data from the first third-party server as matching the entity in the list of entities in the dataset base on a response to the query from the second third-party server.

15 . The system of claim 14 , wherein the one or more processors generate the alert is responsive to verifying the entity as matching the entity in the list of entities.

16 . The system of claim 14 , wherein the one or more processors are configured to:

compute a first score for the event and a second score for matching the entity identified in the data to the entity in the list of entities in the dataset, wherein the alert is generated responsive to the first score and the second score satisfying a threshold criteria.

17 . The system of claim 10 , wherein to detect the event, the one or more processors are configured to:

receive content from a third party server including one or more identifiers of the entity and one or more metrics corresponding to the event;

normalize the one or more metrics;

determine that the normalized one or more metrics satisfy a criterion for identifying the presence of the event;

compute a match score based on the one or more identifiers being associated with the entity from the list of entities included in the dataset; and

detect the event associated with the entity responsive to the match score satisfying a threshold criteria and the normalized one or more metrics satisfying the criterion.

18 . The system of claim 17 , wherein to generate the alert, the one or more processors are configured to:

apply data corresponding to the event and one or more values from fields retrieved from an account with the second computing system to a machine learning model trained to generate recommendations for corresponding events; and

generate the alert to include a recommendation corresponding to an alternative entity with respect to the entity.

19 . A non-transitory computer readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to:

establish a connection between a first computing system and an application hosted on one or more servers of a second computing system in response to receiving a first application program interface (API) call at the first computing system;

retrieve, responsive to receiving a second API call at an API gateway circuit, a dataset comprising a list of entities from a data store maintained by the application, the list of entities associated with an account holder of an account with the application, wherein retrieving the dataset comprises:

determine, based on information in the second API call, at least one circuit of a plurality of circuits internal to the API gateway circuit configured to process the second API call;

route, via the API gateway circuit, the second API call to the at least one circuit; and

receive, via the at least one circuit, the dataset as API response data;

detect an event associated with an entity of the list of entities, based on the dataset received as the API response data and data from a third-party server;

generate an alert corresponding to the event for rendering at a user interface corresponding to the first computing system; and

responsive to a user interaction with the alert at the user interface, execute, using the at least one circuit, a transaction with the entity associated with the event.

20 . The non-transitory computer readable medium of claim 19 , wherein to detect the event, the instructions cause the one or more processors to:

receive content from a third party server including one or more identifiers of the entity and one or more metrics corresponding to the event;

normalize the one or more metrics;

determine that the normalized one or more metrics satisfy a criterion for identifying the presence of the event;

compute a match score based on the one or more identifiers being associated with the entity from the list of entities included in the dataset; and

detect the event associated with the entity responsive to the match score satisfying a threshold criteria and the normalized one or more metrics satisfying the criterion.