Methods and systems for application program interface management

1. A method comprising:

receiving, by a management device from a client device, a command for an implementation device to perform a code commit comprising an Application Program Interface (API) update;

determining, based on the API update modifying a visibility attribute of a portion of the API from Public to Private that the API update violates one or more rules of an API governance policy, wherein the one or more rules ocmprises a deprecation policy; and

determining, based on the API update violating the one or more rules of the API governance policy, that performance of the code commit by the implementation device is to be denied; wherein the API update is not committed to the implementation device;

wherein determining that the API update violates the one or more rules comprises determining whether the API update removes the portion of the API in violation of the deprecation policy by:

determining a date of deprecation associated with the portion of the API;

determining a deprecation period for the portion of the API; and

determining whether a time period between a date of the API update and the date of deprecation exceeds the deprecation period.

2. The method of claim 1 , wherein determining that the API update violates the one or more rules comprises determining whether a version number associated with the API update is incremented according to the one or more rules.

3. The method of claim 1 , wherein the portion of the API is a non-deprecated portion of the API.

4. The method of claim 1 , wherein determining that the API update violates the one or more rules comprises: determining that a documentation associated with the portion of the API is updated.

5. The method of claim 1 , wherein determining that the API update violates the one or more rules comprises: determining that the portion of the API is associated with a test suite.

6. The method of claim 1 , wherein: the client device comprises at least one of: a code generation device, a code management device, or an API development device; the management device comprises at least one of: an interface device, a version control device, or a version control system; and the implementation device comprises at least one of: a code repository, a code executor, or a production server.

7. A method comprising:

receiving, by a management device from a client device, a command for an implementation device to perform an action with a version control system, wherein the action is associated with an Application Program Interface (API) update; determining, based on the API update not modifying a visibility attribute of a portion of the API from Public to Private, that the API update does not violate one or more rules of an API governance policy, wherein the one or more rules comprises a deprecation policy; and allowing the implementation device to perform the action with the version control system based on the API update not violating the one or more rules of the API governance policy;

wherein determining that the API update does not violate the one or more rules comprises determining whether the API update removes the portion of the API in violation of the deprecation policy by: determining a date of deprecation associated with the portion of the API; determining a deprecation period for the portion of the API; and determining whether a time period between a date of the API update and the date of deprecation exceeds the deprecation period.

8. The method of claim 7 , wherein the action comprises a code commit to the version control system.

9. The method of claim 7 , wherein the action comprises a code pull from the version control system.

10. The method of claim 7 , wherein the action comprises a deployment to a server.

11. The method of claim 7 , wherein determining that the API update does not violate the one or more rules comprises determining whether a version number associated with the API update is incremented according to the one or more rules.

12. The method of claim 7 , wherein the portion of the AP′ is a non-deprecated portion of the API.

13. The method of claim 7 , wherein determining that the API update does not violate the one or more rules comprises: determining that a documentation associated with the portion of the API is not updated.

14. The method of claim 8 , wherein determining that the API update does not violate the one or more rules comprises: determining that the portion of the API is not associated with a test suite.

15. A method comprising: receiving, by a management device from a client device, a command for a implementation device to perform an action associated with an Application Program Interface (API) update and a portion of the API; determining that the API update does not deprecate the portion of the API, determining, based on the API update not deprecating the portion of (the API, that the API update violates one or more rules of an API governance policy, wherein the one or more rules comprises a deprecation policy; and denying, by the management device, performance of the action by the implementation device, based on the API update violating the one or more rules of the API governance policy;

wherein determining that the API update violates the one or more rules comprises determining whether the API update removes the portion of the API in violation of the deprecation policy by: determining a date of deprecation associated with the portion of the API; determining a deprecation period for the portion of the API; and determining whether a time period between a date of the API update and the date of deprecation exceeds the deprecation period.

16. The method of claim 15 , wherein the action comprises one or more of a code commit, a code pull, or a deployment to a server.