Get Account Information

The Get Account Information operation returns the sku name and account kind for the specified account.
The Get Account Information operation is available on service versions beginning with version 2018-03-28.

Request

The Get Account Information request may be constructed using a valid request that is authenticated using Shared Key or SAS authentication.
By adding a restype value of account and comp value of properties, the request will use the Get Account Information API. An example is shown.

Method Request URI HTTP Version
GET/HEAD https://myaccount.blob.core.windows.net/?restype=account&comp=properties HTTP/1.1
GET/HEAD https://myaccount.blob.core.windows.net/?restype=account&comp=properties&sv=myvalidsastoken HTTP/1.1
GET/HEAD https://myaccount.blob.core.windows.net/mycontainer/?restype=account&comp=properties&sv=myvalidsastoken HTTP/1.1
GET/HEAD https://myaccount.blob.core.windows.net/mycontainer/myblob?restype=account&comp=properties&sv=myvalidsastoken HTTP/1.1

URI Parameters

The following additional parameters may be specified on the request URI.

Parameter Description
restype Required. The restype parameter value must be account.
comp Required. The comp parameter value must be properties.

Request Headers

The following table describes required and optional request headers.

Request Header Description
Authorization Required. Specifies the authentication scheme, account name, and signature. For more information, see Authentication for the Azure Storage Services.
Date or x-ms-date Required. Specifies the Coordinated Universal Time (UTC) for the request. For more information, see Authentication for the Azure Storage Services.
x-ms-version Required for all authenticated requests. Specifies the version of the operation to use for this request. For this operation, the version must be 2018-03-28 or newer. For more information, see Versioning for the Azure Storage Services.

Request Body

None.

Response

The response includes an HTTP status code and a set of response headers.

Status Code

A successful operation returns status code 200 (OK).

For information about status codes, see Status and Error Codes.

Response Headers

The response for this operation includes the following headers. The response may also include additional standard HTTP headers. All standard headers conform to the HTTP/1.1 protocol specification.

Response header Description
x-ms-request-id This header uniquely identifies the request that was made and can be used for troubleshooting the request. For more information, see Troubleshooting API Operations.
x-ms-version Version 2009-09-19 and newer. Indicates the version of the Blob service used to execute the request.
Date A UTC date/time value generated by the service that indicates the time at which the response was initiated.
Content-Length The length of the request body. For this operation, the content length will always be zero.
x-ms-sku-name This header identifies the sku name of the specified account.
x-ms-account-kind This header identifies the account kind of the specified account. The possible values are Storage, BlobStorage, and StorageV2. Please note that we distinguish between GPv1 and GPv2 storage accounts with the substring, V2, for GPv2 accounts.

Response Body

None.

Sample Response

Response Status:  
HTTP/1.1 200 OK  
  
Response Headers:  
Date: Sat, 28 Mar 2018 12:43:08 GMT  
x-ms-version: 2018-03-28  
Server: Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0  
Content-Length: 0  
x-ms-sku-name: Standard_LRS  
x-ms-account-kind: StorageV2  

Authorization

The storage account owner and users with valid SAS tokens may call this operation. In this context, a valid SAS token must have at least one available permission for the resource specified in the SAS token.

Remarks

The URL path of the request does not affect the information given by this operation. Its purpose is to allow the request to correctly authorize with a SAS token that specifies the allowed resource.
The resource specified need not exist for this operation to succeed. For example, a SAS token generated with a non-existent blob and valid permissions will succeed with a URL path that includes the correct account name, the correct container name, and the non-existent blob's name.