Systems and methods for api request conversion

Abstract

A method or system for application program interface (API) request conversion, includes generating a plurality of configuration files, each associated with a different API format. A first API format of the first API request is identified and a first configuration file is identified based on the first API format. A second API request having a second API format is generated by applying the first API request to the first configuration file. A third API request is received and a third API format of the third API request is identified. A second configuration file is identified based on the third API format. A fourth API request is generated having the second API format by applying the third API request to the second configuration file.

What is claimed is: 
     
         1 . A method for application program interface (API) request conversion, comprising:
 generating, by one or more processors, a plurality of configuration files, each configuration file associated with a different API format;   receiving, by the one or more processors, a first API request;   identifying, by the one or more processors, a first API format of the first API request;   identifying, by the one or more processors, a first configuration file of the plurality of configuration files based on the first API format; and   generating, by the one or more processors, a second API request having a second API format by applying the first API request to the first configuration file.   
     
     
         2 . The method of  claim 1 , further comprising:
 identifying, by the one or more processors, an endpoint at which the first API request is directed;   retrieving, by the one or more processors, data from the endpoint based on the second API request having the second API format;   converting, by the one or more processors, the data from the endpoint into the first format; and   transmitting, by the one or more processors, the data from the endpoint in the first format.   
     
     
         3 . The method of  claim 1 , further comprising:
 identifying, by the one or more processors, an endpoint at which the first API request is directed;   retrieving, by the one or more processors, data from the endpoint based on the second API request having the second API format; and   transmitting, by the one or more processors, the data from the endpoint in the second format.   
     
     
         4 . The method of  claim 1 , wherein identifying the first API format comprises:
 receiving, by the one or more processors, an indication of a source of the first API request; and   identifying, by the one or more processors, the first API format based on the source of the first API request.   
     
     
         5 . The method of  claim 1 , wherein generating the second API request comprises:
 parsing, via the configuration file and by the one or more processors, the first API request to identify first one or more parameters;   comparing, via the configuration file and by the one or more processors, the first one or more parameters to a data structure, the data structure comprising a plurality of parameters associated with the second API format; and   generating, via the configuration file and by the one or more processors, second one or more parameters associated with the second API format based on the comparison of the first one or more parameters to the data structure.   
     
     
         6 . The method of  claim 1 , wherein the second API format is one of Extensible Markup Language, Yet another markup language, or JavaScript Object Notation. 
     
     
         7 . The method of  claim 1 , wherein the first API request comprises authentication information in the first format, and wherein the second API request comprises the authentication information in the second format. 
     
     
         8 . The method of  claim 1 , wherein generating the second API request comprises:
 obtaining, by the one or more processors, endpoints from which to receive data by recursively applying, by the one or more processors, the first API request to the first configuration file.   
     
     
         9 . The method of  claim 8 , wherein recursively applying the first API request to the first configuration file comprises:
 obtaining variables indicating endpoints to specify in an API request by applying the first API request to the first configuration; and   applying the first API request to the first configuration file for a second time but with the obtained variables indicating the endpoints.   
     
     
         10 . The method of  claim 1 , further comprising:
 parsing, via the configuration file by the one or more processors, the first API request to identify first one or more parameters;   comparing, via the configuration file by the one or more processors, the first one or more parameters to a data structure, the data structure comprising a plurality of parameters associated with the second API format; and   determining, via the configuration file by the one or more processors, second one or more parameters of the first one or more parameters that do not correspond to a parameter of the plurality of parameters based on the comparison of the first one or more parameters.   
     
     
         11 . The method of  claim 1 , wherein generating the second API request comprises:
 parsing, via the configuration file by the one or more processors, the first API request to identify first one or more parameters;   comparing, via the configuration file by the one or more processors, the first one or more parameters to a data structure, the data structure comprising a plurality of parameters associated with the second API format; and   determining, via the configuration file by the one or more processors, second one or more parameters of the first one or more parameters that do not correspond to a parameter of the plurality of parameters based on the comparison of the first one or more parameters;   wherein the method further comprises:   generating, by the one or more processors, an alert indicating that the second one or more parameters could not be transformed into the second format; and   displaying, by the one or more processors, the alert on a user interface.   
     
     
         12 . The method of  claim 1 , further comprising:
 receiving, by the one or more processors, a fifth API request having a fifth format;   comparing, by the one or more processors, an identification of the fifth format to a database;   determining, by the one or more processors, that there is not a configuration file associated with the fifth format based on the comparison of the identification of the fifth format to the database;   generating, by the one or more processors, an alert indicating that there is not a configuration file associated with the fifth format; and   displaying, by the one or more processors, the alert on a user interface.   
     
     
         13 . The method of  claim 1 , wherein the first API request comprises authentication information appended to the first API request, and wherein the authentication information is transmitted to an endpoint without being converted to another format. 
     
     
         14 . The method of  claim 1 , wherein generating the second API request comprises generating an array comprising values from a plurality of locations of an endpoint. 
     
     
         15 . A system for application program interface (API) request conversion, the system comprising:
 one or more processors; and   memory coupled to the one or more processors and storing instructions that, when executed by the one or more processors, cause the one or more processors to:   generate a plurality of configuration files, each configuration file associated with a different API format;   receive a first API request;   identify a first API format of the first API request;   identify a first configuration file of the plurality of configuration files based on the first API format; and   generate a second API request having a second API format by applying the first API request to the first configuration file.   
     
     
         16 . The system of  claim 15 , wherein the instructions, when executed, further cause the processor to:
 identify an endpoint at which the first API request is directed;   retrieve data from the endpoint based on the second API request having the second API format;   convert the data from the endpoint into the first format; and   transmit the data from the endpoint in the first format.   
     
     
         17 . The system of  claim 15 , wherein the instructions, when executed, further cause the processor to:
 identify an endpoint at which the first API request is directed;   retrieve data from the endpoint based on the second API request having the second API format; and   transmit the data from the endpoint in the second format.   
     
     
         18 . The system of  claim 15 , wherein the instructions, when executed, cause the processor to identify the first API format:
 receiving an indication of a source of the first API request; and   identifying the first API format based on the source of the first API request.   
     
     
         19 . The system of  claim 15 , wherein the second API format has a different structure than the first API format. 
     
     
         20 . The system of  claim 15 , wherein generating the second API request comprises:
 parsing, via the configuration file, the first API request to identify first one or more parameters;   comparing, via the configuration file, the first one or more parameters to a data structure, the data structure comprising a plurality of parameters associated with the second API format; and   generating, via the configuration file, second one or more parameters associated with the second API format based on the comparison of the first one or more parameters to the data structure.