Integrates with
account required
Plesk
Plesk deployment connects with XML API, lists subscriptions and domains, reads the current certificate, installs a replacement PEM, binds it to the site, verifies the public TLS endpoint, stores the previous certificate for rollback, and repeats the path on renew.
Verification: test_verified. Connection: unknown. Credentials: none. Live E2E: no.
Plesk host/API key and a disposable subscription with a TLS endpoint are not configured.
What sslcertificates.io can do
Plesk deployment connects with XML API, lists subscriptions and domains, reads the current certificate, installs a replacement PEM, binds it to the site, verifies the public TLS endpoint, stores the previous certificate for rollback, and repeats the path on renew. Capabilities: discover_subscriptions, discover_domains, discover_certs, install, bind, tls_verify, rollback, renew. Authentication uses api_key.
Required permissions
Subscription-limited API user. The platform must not receive admin credentials for unrelated subscriptions.
Setup
Open Dashboard → Integrations → Plesk. Enter the credentials described on this page. Values are encrypted at rest and never shown again. Run Test connection. Discovery runs only after authentication succeeds. Select a discovered resource. Do not paste opaque IDs unless the provider cannot enumerate them. Perform the certificate or notification action, then confirm the external system matches. Disconnect removes stored credentials and owned test resources created by sslcertificates.io.
Known limitations
A 200 from the install packet is not success. Success is a TLS handshake showing the new fingerprint.
Official sources
Fact checked 2026-09-20. https://docs.plesk.com/en-US/obsidian/api-rpc/ Plesk is a trademark of its owner. sslcertificates.io is not a partner or certified reseller unless a written agreement exists.
Capabilities
Connect
Plesk is a trademark of its owner. sslcertificates.io is not a partner or certified reseller unless a written agreement exists.