Industry opinionated API managed service

1. A method comprising:

receiving a request from a client that includes a set of application programming interface (API) parameters comprising an industry type selection;

creating a client-specific API based on an industry standard API corresponding to the industry type selection;

deploying, by a processing device, an API managed service on an operational cloud based on the set of API parameters, wherein the API managed service comprises the client-specific API and the deploying comprises provisioning a set of backend resources on the operational cloud to support the client-specific API; and

processing, by the API managed service, one or more commands using the client-specific API, wherein the client-specific API utilizes the provisioned set of backend resources to communicate with the industry standard API.

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

accessing a set of business process configuration parameters based on the industry type selection;

accessing a set of opinionated API libraries based on the industry type selection;

providing a user interface to the client that includes one or more client selection options based on the set of business process configuration parameters and the set of opinionated API libraries;

receiving a set of client selections responsive to providing the user interface to the client; and

customizing the API managed service based on the set of client selections.

3. The method of claim 2 , further comprising:

providing, responsive to customizing the API managed service, an opinionated API to the client;

receiving a set of logic changes from the client in response to providing the opinionated API; and

modifying the opinionated API based on the set of logic changes, wherein the modified opinionated API is the client-specific API.

4. The method of claim 1 , further comprising:

wherein at least one API parameter from the set of API parameters is selected from the group consisting of an availability zone, a scale, a security level, and an endpoint name; and

creating the client-specific API based on the at least one API parameter.

5. The method of claim 1 , wherein the request is a first request and the client is a first client, the method further comprising:

receiving a second request from the first client to interface with a second client through the API managed service, wherein the second request includes a token that identifies both the first client and the second client; and

establishing a connection between the first client and the second client in response to determining that the second client is authorized to interface with the first client.

6. The method of claim 5 wherein the second client connects with the first client through the industry standard API.

7. The method of claim 6 wherein the industry standard API is based on a banking industry type.

8. A system comprising:

a processing device; and

a memory to store instructions that, when executed by the processing device cause the processing device to:

receive a request from a client that includes a set of application programming interface (API) parameters comprising an industry type selection;

create a client-specific API based on an industry standard API corresponding to the industry type selection;

deploy an API managed service on an operational cloud based on the set of API parameters, wherein the API managed service comprises the client-specific API and the deployment comprises provisioning a set of backend resources on the operational cloud to support the client-specific API; and

process, by the API managed service, one or more commands using the client-specific API, wherein the client-specific API utilizes the provisioned set of backend resources to communicate with the industry standard API.

9. The system of claim 8 , wherein the processing device, responsive to executing the instructions, further causes the system to:

access a set of business process configuration parameters based on the industry type selection;

access a set of opinionated API libraries based on the industry type selection;

provide a user interface to the client that includes one or more client selection options based on the set of business process configuration parameters and the set of opinionated API libraries;

receive a set of client selections responsive to providing the user interface to the client; and

customize the API managed service based on the set of client selections.

10. The system of claim 9 , wherein the processing device, responsive to executing the instructions, further causes the system to:

provide, responsive to customizing the API managed service, an opinionated API to the client;

receive a set of logic changes from the client in response to providing the opinionated API; and

modify the opinionated API based on the set of logic changes, wherein the modified opinionated API is the client-specific API.

11. The system of claim 8 , wherein the processing device, responsive to executing the instructions, further causes the system to:

wherein at least one API parameter from the set of API parameters is selected from the group consisting of an availability zone, a scale, a security level, and an endpoint name; and

create the client-specific API based on the at least one API parameter.

12. The system of claim 8 , wherein the request is a first request and the client is a first client, and wherein the processing device, responsive to executing the instructions, further causes the system to:

receive a second request from the first client to interface with a second client through the API managed service, wherein the second request includes a token that identifies both the first client and the second client; and

establish a connection between the first client and the second client in response to determining that the second client is authorized to interface with the first client.

13. The system of claim 12 wherein the second client connects with the first client through the industry standard API that is based on a banking industry type.

14. A non-transitory computer readable medium, having instructions stored thereon which, when executed by a processing device, cause the processing device to:

receive a request from a client that includes a set of application programming interface (API) parameters comprising an industry type selection;

create a client-specific API based on an industry standard API corresponding to the industry type selection;

deploy, by the processing device, an API managed service on an operational cloud based on the set of API parameters, wherein the API managed service comprises the client-specific API and the deployment comprises provisioning a set of backend resources on the operational cloud to support the client-specific API; and

process, by the API managed service, one or more commands using the client-specific API, wherein the client-specific API utilizes the provisioned set of backend resources to communicate with the industry standard API.

15. The non-transitory computer readable medium of claim 14 , wherein to implement the API managed service, the processing device is to:

access a set of business process configuration parameters based on the industry type selection;

access a set of opinionated API libraries based on the industry type selection;

provide a user interface to the client that includes one or more client selection options based on the set of business process configuration parameters and the set of opinionated API libraries;

receive a set of client selections responsive to providing the user interface to the client; and

customize the API managed service based on the set of client selections.

16. The non-transitory computer readable medium of claim 15 , wherein the processing device is to:

provide, responsive to customizing the API managed service, an opinionated API to the client;

receive a set of logic changes from the client in response to providing the opinionated API; and

modify the opinionated API based on the set of logic changes, wherein the modified opinionated API is the client-specific API.

17. The non-transitory computer readable medium of claim 14 , wherein at least one API parameter from the set of API parameters is selected from the group consisting of an availability zone, a scale, a security level, and an endpoint name, and wherein the processing device is to:

create the client-specific API based on the at least one API parameter.