Use this API to update user’s storage, users by assigning a different plan to a user account.
- Authentication token:
The reseller’s authentication token to authorize use of the APIs this must be passed as type string. - Email:
Registration email for the account you wish to upgrade as type string. - Plan ID:
The plan you wish to assign/upgrade the user to. You will need to create plans on the reseller system prior using this option and pass the ID number as an integer.
Upgrading the account via will not change the expiry date of the account. To update this information, you will need to call the Change Account Expiry Date API.
| Code | Message | Comments |
|---|---|---|
| 1000 | The account has been upgraded successfully | Action successful |
| 1002 | Invalid Authentication Token | The authentication token is incorrect, please check it and try again |
| 1003 | Invalid Email or Email does not exist | Make sure that the email address is in its correct format; example someone@company.com and that you have a registered account with that email |
| 1003 | Invalid Email, Email does not belong to you | The email specified is not a user under your reseller account |
| 1006 | The specified plan id does not exist. | The plan id is invalid |
| 1006 | The specified plan id does not belong to this authentication token | The plan ID is not associated to your reseller account |
| 1006 | In order to add a business account, you’ll need to purchase business accounts | You will need to purchase a business account via upgrade in the reseller console to proceed |
| 1006 | In order to add a business account with instant storage, you’ll need to purchase instant storage | You will need to purchase a instant storage via upgrade in the reseller console to proceed |
| 1007 | General Error. DB error | Unexpected database error, if this error occurs, try again later |
| 1007 | General Error. Failed to upgrade account | If you receive this error, please contact support |
| 1007 | General Exception | If you receive this error, please contact support |
The following is a sample SOAP 1.2 request and response. The placeholders shown need to be replaced
with actual values.
POST /Services/Reseller/Service.asmx HTTP/1.1
Host: www.zoolz.com
Content-Type: application/soap+xml; charset=utf-8
Content-Length: length
SOAPAction: “Zoolz/UpgradeAccount”
<?xml version=”1.0″ encoding=”utf-8″?>
<soap12:Envelope xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”
xmlns:xsd=”http://www.w3.org/2001/XMLSchema”
xmlns:soap12=”http://www.w3.org/2003/05/soap-envelope”>
<soap12:Body>
<UpgradeAccount xmlns=”Zoolz”>
<authToken>string</authToken>
<email>string</email>
<planID>int</planID>
</UpgradeAccount>
</soap12:Body>
</soap12:Envelope>
HTTP/1.1 200 OK
Content-Type: application/soap+xml; charset=utf-8
Content-Length: length
<?xml version=”1.0″ encoding=”utf-8″?>
<soap12:Envelope xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”
xmlns:xsd=”http://www.w3.org/2001/XMLSchema”
xmlns:soap12=”http://www.w3.org/2003/05/soap-envelope”>
<soap12:Body>
<UpgradeAccountResponse xmlns=”Zoolz”>
<UpgradeAccountResult>
<Code>Success or MissingParameters or InvalidAuth or InvalidEmail or
InvalidPassword or UsedEmail or PlanError or GeneralError</Code>
<Message>string</Message>
</UpgradeAccountResult>
</UpgradeAccountResponse>
</soap12:Body>
</soap12:Envelope>