Skip to Content

Announcing New Restrictions on API Token Names During Token Creation

18 February 2026

As of Control-M Automation API release 9.0.22.110 (of May 2026), new restrictions are planned for API Token names during creation of new tokens, either through the Web UI (see Creating an API Token) or through Control-M Automation API (see authentication token::create). This change is introduced to strengthen security and support consistent, secure handling of API tokens.

With these changes, all new API Token names can contain only alphanumeric characters, underscores (_), or hyphens (-). No other special characters are supported in new API Token names.

Existing tokens are not impacted by these new restrictions.

You might need to prepare in advance for this change if you have an automated mechanism for creation of API tokens, by adjusting the patterns that you use for token names.

 

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

Control-M