The XML API protocol was designed to support interaction between Plesk
and third-party software remotely. To perform an operation through XML
API, you should send a specifically-structured HTTP message to a
particular Plesk endpoint
receives the message, transforms the message into operation
instructions, attempts to perform the operations, and returns operation
statuses and details. For more information about packets structure and
messages transport, see Client-Server Model and XML API
API errors are generally returned in the language that is selected as default in Plesk. However, not all error messages were translated, so some messages may be returned in English.
Note: The XML API protocol is OS-agnostic. You are free to use it on Plesk for Windows servers and for Linux servers.
At the moment, the use of the XML API protocol is allowed to Administrator, resellers and customers. These users are provided with programmatic means of managing various Plesk objects they own.
- Administrator is allowed to perform all operations of whatever version of all available protocol versions.
- Resellers have access to a limited number of operations within each particular version of XML API. When using a reseller account, a strict requirement is that the option Ability to use XML API is selected in the reseller subscription properties, on the Permissions tab.
- Customers have access to a limited number of operations within each particular version of XML API. Access to XML API is granted to all customers by default and it cannot be turned off.
Note: You can prohibit access to Plesk through XML API or restrict access by IP addresses. Learn more in the Administrator’s Guide, section Restricting Access via XML API.
Plesk XML API protocol evolves in sync with Plesk constantly: When new features appear in Plesk, they are implemented in the protocol. Here are the versions of XML API protocol recommended for use with the later versions of Plesk:
|Plesk version||XML API version|
|Plesk 7.5.4 for Linux/Unix||220.127.116.11|
|Plesk 7.5.6 for Windows||18.104.22.168|
|Plesk 8.0 for Linux/Unix | Plesk 7.6 for Windows||22.214.171.124, 126.96.36.199 (updated)|
|Plesk 7.6.1 for Windows||188.8.131.52|
|Plesk 8.0.1 for Linux/Unix||184.108.40.206|
|Plesk 8.1.0 for Linux/Unix | Plesk 8.1.0 for Windows||220.127.116.11|
|Plesk 8.1.1 for Linux/Unix | Plesk 8.1.1 for Windows||18.104.22.168|
|Plesk 8.2 for Linux/Unix | Plesk 8.2 for Windows||22.214.171.124|
|Plesk 8.3 for Linux/Unix | Plesk 8.3 for Windows||126.96.36.199|
|Plesk 8.4 for Linux/Unix | Plesk 8.6 for Linux/Unix | Plesk 8.4 for Windows | Plesk 8.6 for Windows||188.8.131.52|
|Plesk Onyx 17.0||184.108.40.206|
|Plesk Onyx 17.5||220.127.116.11|
|Plesk Onyx 17.8||18.104.22.168|
Note: Starting from Plesk 12, the version attribute can be omitted. And we strongly recommend that you omit it. In this case, the latest available version will be used. This will help you ensure that your code is operable after switching to a new version of Plesk.
XML API guide has two conceptual topics: GUIDs and descriptors. The first one, GUIDs, concerns identifying objects in Plesk, and the second one defines a way to retrieve currently supported object properties. You should read about them in sections GUIDs Overview and Descriptors Overview to efficiently work with the protocol.