Remove Reseller Privileges — unsetupreseller

To use the XML API to perform the unsetupreseller function from within your custom script:

• Append the /xml-api/unsetupreseller function call name, plus the required variables (see below), to a URL which includes the address of your server.

• For example, on a server whose hostname is example.com, you would include the following string in your script: https://example.com:2087/xml-api/unsetupreseller

• You need to be logged in with the proper permissions in order to call a function. See our document about Authenticating API Function Calls for more information about authenticating APIs from within a script.

• You can also perform the function by entering the string in your web browser's address bar. This may be useful for testing the function call and viewing its output.

To use the JSON API to perform the unsetupreseller function from within your custom script:

• Append the /json-api/unsetupreseller function call name, plus the required variables (see below), to a URL which includes the address of your server.

• For example, on a server whose hostname is example.com, you would include the following string in your script: https://example.com:2087/json-api/unsetupreseller

• You need to be logged in with the proper permissions in order to call a function. See our document about Authenticating API Function Calls for more information about authenticating APIs from within a script.

• You can also perform the function by entering the string in your web browser's address bar. This may be useful for testing the function call and viewing its output.

Calling the URL https://example.com:2087/xml-api/unsetupreseller?user=bob in WebHost Manager will produce output similar to:

<unsetupreseller>
     <result>
            <status>1</status>
            <statusmsg/>
      </result>
</unsetupreseller>

Calling the URL https://example.com:2087/json-api/unsetupreseller?user=bob in WebHost Manager will produce output similar to:

{
   "result":[
      {
         "status":1,
         "statusmsg":null
      }
   ]
}