Systems and methods for API forge accelerator

1 . A method for developing an application programming interface (API), by a computing system running an API Forge Accelerator, comprising:

receiving, by the API Forge Accelerator, a request for generating an API for a service based on a type of a first gateway, wherein the request indicates a selection of the first gateway among a plurality of gateways integrated with the API Forge Accelerator;

generating, by the API Forge Accelerator and based on a specific gateway, a specification template corresponding to the specific gateway for generating the API, wherein the specification template indicates specification information that is used for the API generation;

obtaining, by the API Forge Accelerator and based on the specification template, the specification information from user input and API tools; and

generating, by the API Forge Accelerator and based on the specification information, the API for the service.

2 . The method of claim 1 , wherein obtaining the specification information from the user input and the API tools further comprises:

obtaining, by the API Forge Accelerator, a uniform resource locator (URL) to a specification corresponding to the API, wherein the specification defines operations and formats corresponding to the API; and

obtaining, by the API Forge Accelerator via the URL, the specification corresponding to the API using a first API tool among the API tools.

3 . The method of claim 1 , further comprises:

verifying, by the API Forge Accelerator, that design guidelines are being followed.

4 . The method of claim 3 , further comprising:

displaying, by the API Forge Accelerator and based on determining that the verification fails, one or more corrective actions on a user device.

5 . The method of claim 1 , wherein the specification template includes one or more user interface (UI) forms indicating the specification information needed for the API generation, and wherein obtaining the specification information from the user input and the API tools further comprises:

obtaining, by the API Forge Accelerator, the specification information requested by the one or more UI forms corresponding to the specific gateway via the user input and information obtained from the API tools.

6 . The method of claim 5 , wherein the one or more UI forms further indicates information needed for creating one or more API artifacts for the API.

7 . The method of claim 6 , wherein generating the API for the service further comprises:

generating, by the API Forge Accelerator, documentations for the one or more API artifacts corresponding to the specific gateway.

8 . The method of claim 1 , wherein generating the API for the service further comprises:

generating, by the API Forge Accelerator and using one or more API tools among the API tools, source code for the API in accordance with predefined standard template design; and

updating, by the API Forge Accelerator and based on the generated source code, corresponding source codes associated with the API in a version control system (VCS).

9 . The method of claim 1 , further comprising:

determining, by the API Forge Accelerator, whether a continuous integration/continuous deployment (CI/CD) pipeline exists for the API; and

creating, by the API Forge Accelerator, the CI/CD pipeline, based on determining that there is no existing CI/CD pipeline for the API.

10 . The method of claim 9 , further comprising:

prompting, by the API Forge Accelerator, the CI/CD pipeline to kick off.

11 . The method of claim 10 , wherein the CI/CD pipeline comprises operations of:

retrieving source code from a version control system (VCS);

executing build scripts to build/package the source code;

performing a code quality check;

conducting a static code analysis using an external tool;

saving packaged code to an artifact repository;

deploying the code to the specific gateway;

performing integration testing;

deploying the code to additional environments; and

performing penetration testing.

12 . The method of claim 11 , wherein based on any of the operations by the CI/CD pipeline failing, the API Forge Accelerator notifies the failure and proceeds to a next operation after the failure is fixed.

13 . The method of claim 1 , further comprising:

receiving, by the API Forge Accelerator, a second request from a user device to modify a value for a proxy associated with the API;

updating, by the API Forge Accelerator, based on the second request, configuration of the proxy in a VCS to modify the value;

running, by the API Forge Accelerator, a CI/CD pipeline to automatically sense and deploy the modification of the value to the specific gateway; and

returning, by the API Forge Accelerator, a success message and displaying the message on the user device.

14 . The method of claim 1 , further comprising:

receiving, by the API Forge Accelerator, a query to inspect relationship between two entities among proxies, shared flows, target servers, and backend uniform resource locator (URL) associated with the API;

calling, by the API Forge Accelerator, to a code search tool to determine dependencies among the proxies, shared flows, target servers, and backend URL associated with the API;

receiving, by the API Forge Accelerator, results of the dependencies among the proxies, shared flows, target servers, and backend URL associated with the API; and

generating, by the API Forge Accelerator and based on the results, a relationship diagram on a user device.

15 . The method of claim 1 , further comprising:

providing, by the API Forge Accelerator and to a user device, sample codes to build a test suite using one or more testing frameworks.

16 . An application programming interface (API) Forge Accelerator computing system, comprising:

one or more processors; and

a non-transitory computer-readable medium having processor-executable instructions stored thereon, wherein the processor-executable instructions, when executed by the one or more processors, facilitate:

receiving a request for generating an API for a service based on a type of a first gateway, wherein the request indicates a selection of the first gateway among a plurality of gateways integrated with the API Forge Accelerator;

generating, based on a specific gateway, a specification template corresponding to the specific gateway for generating the API, wherein the specification template indicates specification information that is used for the API generation;

obtaining, based on the specification template, the specification information from user input and API tools; and

generating, based on the specification information, the API for the service.

17 . The API Forge Accelerator computing system of claim 16 , wherein the processor-executable instructions, when executed, further facilitate:

receiving a second request from a user device to modify a value for a proxy associated with the API;

updating, based on the second request, configuration of the proxy in a source control system (VCS) to modify the value;

running, a continuous integration/continuous deployment (CI/CD) pipeline to automatically sense and deploy the modification of the value to the specific gateway; and

returning, a success message and displaying the message on the user device.

18 . The API Forge Accelerator computing system of claim 16 , wherein the processor-executable instructions, when executed, further facilitate:

receiving, a query to inspect relationship between two entities among proxies, shared flows, target servers, and backend uniform resource locator (URL) associated with the API;

calling, to a code search tool to determine dependencies among the proxies, shared flows, target servers, and backend URL associated with the API;

receiving, results of the dependencies among the proxies, shared flows, target servers, and backend URL associated with the API; and

generating, based on the results, a relationship diagram on a user device.

19 . The API Forge Accelerator computing system of claim 16 , wherein the processor-executable instructions, when executed, further facilitate:

providing sample codes to build a test suite using one or more testing frameworks.

20 . A non-transitory computer-readable medium having processor-executable instructions stored thereon, wherein the processor-executable instructions, when executed, facilitate:

receiving a request for generating an application programming interface (API) for a service based on a type of a first gateway, wherein the request indicates a selection of the first gateway among a plurality of gateways integrated with an API Forge Accelerator;

generating, based on a specific gateway, a specification template corresponding to the specific gateway for generating the API, wherein the specification template indicates specification information that is used for the API generation;

obtaining, based on the specification template, the specification information from user input and API tools; and

generating, based on the specification information, the API for the service.