System and method for providing api version control

Abstract

Described herein is a system for providing version control across APIs. In an embodiment, an application of a client device may transmit communications to a service application API that are in a format not accepted by the service application API, using the application API. A central (or public) API may receive the communication transmitted by the application's API. The central API may identify the versions of the application's API and the service application API. The central API may format the communication based on the mapped fields, to a format accepted by the service application API. The central API 106 may forward the formatted communication to the service application.

What is claimed is: 
     
         1 . A method for providing version control, the method comprising:
 determining, based on a request from a client application API to send data in a first format to a service application API associated with a second format, that a version of the client application API is different from the version of the client application;   transforming, based on data fields of the data in the first format mapped to data fields compatible with the version of the service application API, the data in the first format to the second format; and   sending, to the service application API, the transformed data.   
     
     
         2 . The method of  claim 1 , further comprising identifying, via a central API, the service application API from a plurality of service application APIs as the intended recipient of the request based on the data in a first format received from the client application API. 
     
     
         3 . The method of  claim 1 , further comprising sending, via a central API, a response from the service application API to the client device. 
     
     
         4 . The method of  claim 3 , wherein the central API is configured to periodically update versions of at least one of the service application API or the client application API. 
     
     
         5 . The method of  claim 1 , wherein a service application associated with the service application API uses a publish-subscribe messaging system to communicate with other service applications. 
     
     
         6 . The method of  claim 1 , wherein the request from the client application API is associated with a request to generate at least one of a prequalification result for a user related to a product or receive entity-based information associated with the product. 
     
     
         7 . The method of  claim 1 , further comprising causing a service application associated with the service application API to generate, based at least in part on the sending the transformed data to the service application API, a data structure for an entity that facilitates a transaction for a product. 
     
     
         8 . A system for providing version control, the system comprising:
 a memory; and   a processor coupled to the memory, wherein the processor is configured to perform operations comprising:   determining, based on a request from a client application API to send data in a first format to a service application API associated with a second format, that a version of the client application API is different from the version of the client application;   transforming, based on data fields of the data in the first format mapped to data fields compatible with the version of the service application API, the data in the first format to the second format; and   sending, to the service application API, the transformed data.   
     
     
         9 . The system of  claim 8 , the operations further comprising identifying, via a central API, the service application API from a plurality of service application APIs as the intended recipient of the request based on the data in a first format received from the client application API. 
     
     
         10 . The system of  claim 8 , the operations further comprising sending, via a central API, a response from the service application API to the client device. 
     
     
         11 . The system of  claim 10 , wherein the central API is configured to periodically update versions of at least one of the service application API or the client application API. 
     
     
         12 . The system of  claim 8 , wherein a service application associated with the service application API uses a publish-subscribe messaging system to communicate with other service applications. 
     
     
         13 . The system of  claim 8 , wherein the request from the client application API is associated with a request to generate at least one of a prequalification result for a user related to a product or receive entity-based information associated with the product. 
     
     
         14 . The system of  claim 8 , the operations further comprising causing a service application associated with the service application API to generate, based at least in part on the sending the transformed data to the service application API, a data structure for an entity that facilitates a transaction for a product. 
     
     
         15 . A non-transitory computer-readable medium having instructions stored thereon that, when executed by at least one computing device, causes the at least one computing device to perform operations for providing version control, the operations comprising:
 determining, based on a request from a client application API to send data in a first format to a service application API associated with a second format, that a version of the client application API is different from the version of the client application;   transforming, based on data fields of the data in the first format mapped to data fields compatible with the version of the service application API, the data in the first format to the second format; and   sending, to the service application API, the transformed data.   
     
     
         16 . The non-transitory computer-readable medium of  claim 15 , the operations further comprising identifying, via a central API, the service application API from a plurality of service application APIs as the intended recipient of the request based on the data in a first format received from the client application API. 
     
     
         17 . The non-transitory computer-readable medium of  claim 15 , the operations further comprising sending, via a central API, a response from the service application API to the client device. 
     
     
         18 . The non-transitory computer-readable medium of  claim 18 , wherein the central API is configured to periodically update versions of at least one of the service application API or the client application API. 
     
     
         19 . The non-transitory computer-readable medium of  claim 15 , wherein a service application associated with the service application API uses a publish-subscribe messaging system to communicate with other service applications. 
     
     
         20 . The non-transitory computer-readable medium of  claim 15 , wherein the request from the client application API is associated with a request to generate at least one of a prequalification result for a user related to a product or receive entity-based information associated with the product.