Source code conversion from application program interface to policy document

A method for converting source code, comprising:

• receiving, by a code conversion device, source code associated with an application program interface (API) configured to execute on a dedicated runtime infrastructure;
• identifying, by the code conversion device, one or more code sections in the source code that implement one or more function calls associated with one or more function call types;
• generating, by the code conversion device, an executable policy document including machine-readable text based on the one or more code sections implementing the one or more function calls associated with the one or more function call types;
• invoking, by the code conversion device, a validation utility to cross-check the executable policy document against a design document associated with the API;
• and
• deploying, by the code conversion device, the executable policy document in a common runtime environment that includes a shared runtime infrastructure to support multiple executable policy documents based on the validation utility indicating that the executable policy document satisfies functional requirements described in the design document associated with the API.

A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising:

• one or more instructions that, when executed by one or more processors of a code conversion platform, cause the code conversion platform to:
• receive source code associated with multiple application program interfaces (APIs) including at least a first API configured to execute on a first runtime infrastructure and a second API configured to execute on a second runtime infrastructure that is different from the first runtime infrastructure;
• identify, in the source code associated with the multiple APIs, code sections implementing one or more function calls associated with one or more function call types to be converted into executable policy documents;
• generate multiple executable policy documents including machine-readable text that is functionally equivalent to the code sections implementing the one or more function calls associated with the one or more function call types to be converted,
• wherein the multiple executable policy documents include at least a first executable policy document corresponding to the first API and a second executable policy document corresponding to the second API;
• invoke a validation utility to cross-check the multiple executable policy documents against design documents associated with the multiple APIs;
• and
• deploy the multiple executable policy documents in a common runtime environment in which the multiple executable policy documents are configured to execute on a shared runtime infrastructure based on the validation utility indicating that the multiple executable policy documents satisfy functional requirements described in the design documents associated with the multiple APIs.