The set operation is used to modify reseller account settings.
A request XML packet updating settings for a specified reseller account includes the set operation node:
<packet>
<reseller>
<set>
...
</set>
</reseller>
</packet>
The set node is presented by the ResellerSetInput complex type (reseller.xsd
). Its graphical representation is as follows:
reseller.xsd
).reseller.xsd
). To view the structure of this node, refer to the Type ResellerSetGenInfo section.reseller.xsd
). To view the structure of this node, refer to the Limits section.plesk_client.xsd
). To view the structure of this node, refer to the Permissions section.
Important: When creating request packets, put nodes and elements in the order they follow in the packet structure.
The set node of the response packet is structured as follows:
common.xsd
). common.xsd
). Allowed values: ok|error
.common.xsd
).
The following packet updates reseller accounts limits and sets the oversell limits policy for these accounts:
<packet version="1.6.0.2">
<reseller>
<set>
<filter>
<login>JDoe</login>
<login>RRoe</login>
</filter>
<values>
<limits>
<resource-policy>
<oversell>true</oversell>
</resource-policy>
<limit>
<name>disk_space</name>
<value>209715200</value>
</limit>
<limit>
<name>max_dom</name>
<value>50</value>
</limit>
<limit>
<name>max_subdom</name>
<value>250</value>
</limit>
<limit>
<name>max_webapps</name>
<value>30</value>
</limit>
<limit>
<name>max_traffic</name>
<value>209715200</value>
</limit>
<limit>
<name>max_db</name>
<value>30</value>
</limit>
</limits>
</values>
</set>
</reseller>
</packet>
Response:
<packet version="1.6.0.0">
<reseller>
<set>
<result>
<status>ok</status>
<filter-id>JDoe</filter-id>
<id>2</id>
</result>
</set>
</reseller>
</packet>