Use a dedicated API key where your Plesk configuration allows one. Apply appropriate source-address restrictions and ensure the WHMCS server can reach the panel over HTTPS. The module also accepts an administrator username and password when no key is supplied. Keep these credentials out of customer package descriptions and downloadable connector archives.

1. In Domain Nexus Servers, choose Plesk (REST v2 + XML API).
2. Enter Hostname or IP address. A bare hostname uses port 8443; a full URL can specify your actual HTTPS endpoint.
3. Paste the API key. If using the password method, leave the key empty and fill in both Username and Password.
4. If this is also a WHMCS hosting server and you plan to use automatic hosting handoff, select the matching WHMCS Plesk server. Confirm it represents the same machine, not a similarly named replacement.
5. Leave Plesk Subscription Domain empty for your ordinary DNS arrangement. Set it only when you intentionally want new domains created as web aliases of an existing subscription.
6. Save, check the connection and assign it to a controlled test package.

Read an authorised zone and test one temporary TXT change. Inspect the result in Plesk and through the authoritative nameservers. When subscription parking is enabled, separately check the alias's website content and HTTPS certificate. DNS records alone cannot prove a web alias or its certificate works.

If a read works but provisioning fails, review administrator XML API permission, subscription availability and the requested domain's current ownership. The parking setting applies to new aliases; it does not automatically convert existing hosted domains. A domain already attached to another hosting customer needs ownership review before any migration. Use the dedicated parking and hosting-handoff guides for those workflows.

• Use a Plesk subscription as the target for new DNS domain aliases
• Preserve DNS when a parked domain becomes a hosting account
• Add a DNS provider connection and prove that it can manage zones
• Run a controlled DNS provider acceptance check before assigning customer packages

• Plesk: REST API