• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question XML API error

tersor

New Pleskian
We want to automate tasks from Wordpress toolkit via the XML API.
But is seems that managing WordPress installations via XML API is not supported on Plesk 17.x?
Is this correct?

Plesk Onyx version 17.5.3
XML API version 1.6.9.0

The following schemas is present:
$ find . -type f -name "wpinstance.xsd"
./admin/htdocs/schemas/rpc/1.6.7.0/wpinstance.xsd
./admin/htdocs/schemas/rpc/1.6.6.0/wpinstance.xsd

Code:
POST:
<packet>
  <wp-instance>
    <get-list/>
  </wp-instance>
</packet>
RESPONSE:
<?xml version="1.0"?>
<packet version="1.6.9.0">
  <system>
    <status>error</status>
    <errcode>1014</errcode>
    <errtext>Parser error: Request is invalid. Error in line 2: Element 'wp-instance': This element is not expected. Expected is one of ( request-settings, server, customer, webspace, subdomain, dns, db_server, mail, migration, certificate ).</errtext>
  </system>
</packet>

When specifying v1.6.7.0:
Code:
POST:
<packet version="1.6.7.0">
  <wp-instance>
    <get-list/>
  </wp-instance>
</packet>
RESPONSE:
<?xml version="1.0" encoding="UTF-8"?>
<packet version="1.6.7.0">
  <wp-instance>
    <get-list>
      <result>
        <status>error</status>
        <errcode>1017</errcode>
        <errtext>This feature is not supported anymore.</errtext>
      </result>
    </get-list>
  </wp-instance>
</packet>
 
Back
Top