Accounts-account-email-domain-infostore:PUT

From Hostway API Documentation
Revision as of 08:48, 20 May 2013 by Mike.robski (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

= PUT /accounts/{account}/email/{domain}/infostore Change InfoStore quota.

Contents


Request

PUT /accounts/{account}/email/{domain}/infostore

URI Parameters

account - string
domain - string

Request Headers

Authorization - HTTP Authorization header [1]
The Authentication credentials of the client application.
Content-Type
Required. Set this header to application/json; charset=UTF-8


Request Body

{
    "quota": {newQuotaSize}
}
 


Parameters

quota- Integer
The new quota size.

Response

Status Code

200 Ok
Success
400 Bad Request
The format of the request body is invalid or the username does not meet the requirements.
401 Unauthorized
The supplied credentials are invalid or do not provide permissions for this operation.
404 Not Found
The domain name does not exist.

Examples

Failure setting new InfoStore quota with missing required parameter

Request

PUT /accounts/{account}/email/test.com/infostore

{
    "foo": "bar"
}
 

Response

400 Bad Request

{"badRequest": {"message": "POST data error", "code": 400, "details": {"quota": "Required"}}}
 


Failure changing the storage with invalid quota value

Request

PUT /accounts/{account}/email/test.com/infostore
{
    "quota": -1
}
 

Response

400 Bad Request
{"badRequest": {"message": "POST data error", "code": 400, "details": {"quota": "-1 is less than minimum value 0"}}}
 


Failure when trying to change the quota to a value that is less than the current usage

Request

PUT /accounts/{account}/email/test.com/infostore

{
    "quota": 100
}
 

Response

400 Bad Request

{"badRequest": {"message": "POST data error", "code": 400, "details": {"message": "Used storage exceeeds the quota value"}}}
 


Success setting setting new InfoStore quota

Request

PUT /accounts/{account}/email/test.com/infostore

{"quota": 50}
 

Response

204 No Content

See also


blog comments powered by Disqus

Personal tools
Namespaces
Variants
Actions
APIs
Navigation
Toolbox