Control-M Automation API Migration to OpenAPI 3.1

22 June 2025

Announcing the Migration of Control-M Automation API to OpenAPI 3.1

Control-M Automation API is migrating from Swagger 2 to OpenAPI 3.1 in the next major release of Control-M, and the API YAML file, /automation-api/yaml, which is currently in Swagger 2 format, will be based instead on OpenAPI 3.1.

If you build your own REST clients for Control-M Automation API, you must migrate your client to OpenAPI 3.1 to continue working with Control-M Automation API.

To enable you to prepare for this migration, a new YAML file based on the OpenAPI 3.1 standard will be provided in the Control-M Automation API monthly release of August (9.0.22.030) at /automation-api/yaml/v3.

Backward compatibility will be supported in the next major release, but will not be supported in subsequent releases after that.

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*