cPanel Sync Updates

• cPanel for the last 20+ years has used a a username/password combination to access their API. We built our cPanel Sync using this API. While the username/password system worked, it meant you could not change yoru cPanel password and you had to share your password with others (like us) to access your API.

The cPanel Upgrade

• Since cPanel v138, HTTP Basic authentication (username/password in headers) is no longer accepted by default on the cPanel platform.

Upgrading To API Tokens

• MX Guarddog fully supports the new cPanel API Token system. You continue to use the same username, but rather than entering your password you must generate an API token on your cPanel server and provide the token to MX Guarddog to authenticate with your server.

Getting Your API Token

• The cPanel API Token is generated on your server (not MX Guarddog).

  Go to cPanel >> Home >> Security >> Manage API Tokens (or the Security hub's Advanced tab in newer themes) and generate a token.

  You will be asked to enter a description, that is just for your reference. Something like MX Guarddog cPanel Sync.

  cPanel will then show you a 32 digit token, it's shown only once, so store it securely. Use the new token on the MX Guarddog cPanel Sync page and we will start using the token to sync with your server.

  cPanel documentation also covers how to generate an API token, you can find that here: https://docs.cpanel.net/cpanel/meridian/security/managing-ssh-keys-and-api-tokens/

Old cPanel Systems

• If for some reason you are not upgrading your cPanel infrastructure and do not have access to the new API token system you can continue to use your username/password system but after you upgrade your cPanel server to version 138 your system will default to the API token system.

Updated 2026/09/01