Connect PD Plesk DNS to the intended Plesk server using a dedicated XML API secret key prepared for requests from your billing server. The provider form also supports username and password, but a dedicated secret key avoids storing an everyday administrator password for this integration.

Prepare the server connection

Install PD Modules, connect the account holding your licence, then install PD Plesk DNS from the Store and allow the appropriate staff role. Confirm the Plesk hostname, secure API port and the domains the connection should manage.

Ask the responsible Plesk administrator to prepare a secret key for the billing server’s actual outgoing address and intended account. Plesk’s secret-key creation reference describes account and source-address assignment. A customer or reseller key has different permissions from an administrator key; this module’s server-information connection test and each intended operation must be permitted.

Plesk offers the optional Keychain for API Secret Keys extension for managing keys in its interface. Ask the administrator to confirm whether it is installed and suitable for this server. Where it is unavailable, have the administrator use Plesk’s supported key-management process; do not search for an assumed standard API Keys menu or put server commands in customer notes.

Add and test the provider

1. Open Plesk DNS → Providers → Add a provider.
2. Name the connection and enter Plesk hostname, using a name matching the server’s valid certificate.
3. Set Port, normally 8443, and enter API key (secret key).
4. Run Test connection, inspect the result and save the provider.
5. Open Zones, find a known domain and read its records before offering client editing.

The test reads Plesk server information. It does not prove every domain, record write or forwarding action is available. Check the exact refused operation with the administrator rather than granting unrestricted access to clear a warning.

Keep the two APIs distinct

This provider uses Plesk’s XML API authentication. PD Plesk DNS’s own automation token is a separate credential for your integration; it does not replace the provider secret key. Keep both values out of screenshots, tickets and client notes.

If authentication fails after an address change, confirm the key’s allowed source address. For missing domains, use the visibility guide; repeated key creation cannot restore a domain that is absent from Plesk.

See the PD Plesk DNS Blesta guide for related tasks, or explore the module.