Use the module’s automation API for intended DNS integrations without distributing the provider’s Plesk XML API secret key. Module tokens are administrative integration credentials, separate from client portal access.

Create the intended token

1. Open Plesk DNS → Maintenance → API access.
2. Name the integration and choose its required read and/or write scopes.
3. Restrict source addresses where appropriate for the caller.
4. Create the token and save its once-shown value privately.
5. Copy the endpoint displayed for this installation.

Use that displayed endpoint instead of a URL from another billing platform. Revoke and replace a lost token; its original full value cannot be shown again.

Read before writing

Use the documented bearer header or supported alternative token header where the server strips Authorization. Begin with zone and record reads, and get current record references before editing or deleting.

Locks, content policy and managed-record protection remain relevant to supported writes. Native account scope and the existing-domain prerequisite still apply. An integration token cannot make this module create a missing standalone zone.

Reconcile the actual result

An edit can leave both old and new values if the later removal fails. Requested individual TTLs are not sent by this module, so verify actual provider data using the TTL guide. Inspect state before repeating a timed-out write.

Keep authentication, scope, source restriction and provider refusal separate. For token rotation, verify a replacement integration token before retiring the old one. Coordinate the provider XML API secret key separately using the credential guide. Never include either secret in support attachments.

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