Hello,
Here is a sample where we are attempting to set a domain to use a new IP
And here is the response - you can note that there are 2 result nodes while the API standard of all the other commands (and your documentation) only ever should have 1.
Also, I pass in the domain name domainname.com which does exist on the server, and I get back a <filter-id>domainnameid.com<filter-id> and an <id> node, it would appear that the command is using my string value domain name filter as a domain name (site) id instead.
Here is a sample where we are attempting to set a domain to use a new IP
<?xml version="1.0" encoding="UTF-8"?>
<packet version="1.6.3.5">
<site>
<set>
<filter>
<name>domainname.com</name>
</filter>
<values>
<hosting>
<vrt_hst>
<property>
<name>ip_address</name>
<value>10.7.71.240</value>
</property>
</vrt_hst>
</hosting>
</values>
</set>
</site>
</packet>
And here is the response - you can note that there are 2 result nodes while the API standard of all the other commands (and your documentation) only ever should have 1.
<?xml version="1.0" encoding="UTF-8"?>
<packet version="1.6.3.5">
<site>
<set>
<result>
<result>
<status>error</status>
<errcode>1013</errcode>
<errtext>Site does not exist</errtext>
<filter-id>domainname.com</filter-id>
<id>23</id>
</result>
</result>
</set>
</site>
</packet>
Also, I pass in the domain name domainname.com which does exist on the server, and I get back a <filter-id>domainnameid.com<filter-id> and an <id> node, it would appear that the command is using my string value domain name filter as a domain name (site) id instead.