The del operation is used to remove the specified customer account and all its settings from Plesk database.
A request XML packet deleting a customer account from Plesk database includes the del operation node:
<packet version="1.6.3.0">
<customer>
<del>
...
</del>
</customer>
</packet>
The del node does not have a separate type, it is nested within the ClientTypeRequest complex type (client_input.xsd
). The del node has the following graphics representation:
(client_input.xsd
). For more information on filters, refer to the Available Filters section.
The del node of the response packet is structured as follows:
common.xsd
).
A single request packet can delete a single or multiple customer accounts. If multiple customer accounts are deleted, they can be filtered by one parameter at a time:
<packet version="1.6.3.0">
<customer>
<del>
<filter>
<id>1324</id>
<id>1325</id>
</filter>
</del>
</customer>
</packet>
Response:
<packet version="1.6.3.0">
<customer>
<del>
<result>
<status>ok</status>
<id>1324</id>
</result>
<result>
<status>ok</status>
<id>1325</id>
</result>
</del>
</customer>
</packet>
You can use some other filtering parameter:
<packet version="1.6.3.0">
<customer>
<del>
<filter>
<login>technolux</login>
<login>advent</login>
</filter>
</del>
</customer>
</packet>
The following packet is invalid as it uses both id and login in the same filter:
<packet version="1.6.3.0">
<customer>
<del>
<filter>
<id>1324</id>
<login>advent</login>
</filter>
</del>
</customer>
</packet>
To fix this packet, use multiple del sections:
<packet version="1.6.3.0">
<customer>
<del>
<filter>
<id>1324</id>
</filter>
</del>
<del>
<filter>
<login>advent</login>
</filter>
</del>
</customer>
</packet>