Specific account listing

The account listing command allows the user to list the information for a specific storage account.

Note that this request may take two round trips (one trip to obtain the list of storage locations that a storage account has containers in, another trip to obtain the storage account's usage in each storage location).

Base Command :

GET <accesser>:8338/accounts/{account.id}

Table 1. Request Parameter
Request Parameter	Style	Type	Description
Common request headers
ibm-account-id (Optional)	header	String	Optional. Your Bluemix ID, which the system stores. This request header is only available for IAM-authenticated requests.

Table 2. Response Parameters
Response Parameter	Style	Type	Description
Common response headers
Accepted-Ranges	header	String	Only "bytes" is allowed
X-Account-Object-Count	header	Integer	The number of objects in the account.
X-Account-Container-Count	header	Integer	The number of containers.
X-Account-Bytes-Used	header	Integer	The total number of bytes that are stored in Object Storage for the account.
X-Account-Meta-name (Optional)	header	String	The custom account metadata item, where {name} is the name of the metadata item. One x-account-meta-{name} response header appears for each metadata item (for each {name}).
X-Account-Sysmeta-name (Optional)	header	String	The account system metadata. This requires a special permission to be configured for the role for which the authenticated user has been assigned
X-Account-Max-Container-Count (Optional)	header	String	The maximum number of containers for this storage account. The range is 0 to a system-wide upper limit of maximum containers per storage account. Contact Customer Support personnel to determine or change the value of the upper limit of the maximum containers per storage account. If this parameter is not set using the Service API, then the parameter is not returned in the response and the system-wide maximum container limit per storage account applies. Contact Customer Support personnel to determine this value.
X-Timestamp	header	Integer	The date and time in UNIX Epoch time stamp format when the account, container, or object was initially created as a current version. For example, 1440619048 is equivalent to Mon, Wed, 26 Aug 2015 19:57:28 GMT.
X-Account-Meta-Quota-Bytes (Optional)	header	Integer	The number of bytes allocated for this storage account
Per Storage Policy / Vault (Response Body - Optional)
name	body	String	Provisioning code of the storage location (only if the output format is JSON or XML). Will be an empty string if storage location has no associated provisioning code
`id`	body	String	The uuid of the storage location.
object_count	body	Integer	The number of bytes used under this account stored within this vault (only if the output format is JSON or XML)
bytes_used	body	Integer	The number of objects under this account stored within this vault (only if the output format is JSON or XML)
container_count	body	Integer	The number of containers under this account (only if the output format is JSON or XML)
Per Account (Response Body - Optional)
id	body	String	Id of the account (only if the output format is JSON or XML)
object_count	body	Integer	Number of objects within the account (only if the output format is JSON or XML)
bytes_used	body	Integer	Number of bytes within the account (only if the output format is JSON or XML)
container_count	body	String	The number of containers under this account (only if the output format is JSON or XML)
ibm-account-id (Optional)	header	String	Optional. Your IBM Cloud Platform ID stored by the system. This request header is only available for IAM-authenticated requests.

Table 3. HTTP Response Code
HTTP Response Code	Description
200 OK	The account exists and command succeeds
401 Unauthorized	The provided token is invalid or could not be verified with Keystone.
403 Forbidden	The provided token may be valid, but Keystone has reported to Swift that the user lacks the appropriate permission.
404 Not Found	The specific account was not found on the system

Table 4. Role Guidance
Role Guidance	Description
Service User	A user configured at the Manager with a Service User Role

Example Output

Request
GET <accesser>:8338/accounts/731fc6f265cd486d900f16e84c5cb594

Response
HTTP/1.1 200 OK
Content-Length: 158
Accept-Ranges: bytes
X-Account-Object-Count: 0
X-Timestamp: 1458262564.22774
X-Account-Bytes-Used: 0
X-Account-Container-Count: 3
X-Account-Max-Container-Count: 1000
X-Account-Status: ENABLED
Content-Type: application/json; charset=utf-8
X-Trans-Id: txa214ce1fb3614b6aa15e1-0056ec0f3c
Date: Fri, 18 Mar 2016 14:22:52 GMT
{
    "account": {
        "storage_location": [
            {
                "name": "us-standard",
                "id": "b190120d-6bc2-7c06-0105-fbc3fa265865"
                "container_count": 1,
                "object_count": 0,
                "bytes_used": 0
            },
            {
                "name": "us-standard",
                "id": "a200159c-6af2-5d26-9125-acd4dd574877"
                "container_count": 2,
                "object_count": 1,
                "bytes_used": 1000
            }
        ],
        "id": "731fc6f265cd486d900f16e84c5cb594",
        "container_count": 3,
        "object_count": 1,
        "bytes_used": 1000
    }
}