You can call NAS API operations by sending HTTP or HTTPS requests based on URLs. You must include request parameters in URLs. This topic describes the syntax of HTTP or HTTPS requests and provides the endpoints of NAS API.

Sample requests

The following example shows an unencoded URL request to call the CreateFileSystem operation:
&<Common request parameters>
  • http(s) specifies the protocol that is used for the request.
  • specifies the endpoint of NAS API.
  • Action=CreateFileSystem specifies the API operation that you want to call. EncryptType=1, ProtocolType=NFS, and StorageType=Performance specify the parameters that are required for CreateFileSystem.
  • <Common request parameters>: the common request parameters that are specified in the system.


You can send requests over HTTP or HTTPS. If you require higher levels of security, we recommend that you send requests over HTTPS.


The following table describes the endpoints of NAS API. To minimize the network latency, we recommend that you specify the endpoint based on the region where you make API requests.

Region Endpoints
China (Qingdao)
China (Beijing)
China (Zhangjiakou)
China (Hohhot)
China (Ulanqab)
China (Hangzhou)
China (Shanghai)
China (Shenzhen)
China (Heyuan)
China (Guangzhou)
China (Chengdu)
China (Hong Kong)
Japan (Tokyo)
Singapore (Singapore)
Australia (Sydney)
Malaysia (Kuala Lumpur)
Indonesia (Jakarta)
US (Virginia)
US (Silicon Valley)
UK (London)
Germany (Frankfurt)
India (Mumbai)

Request parameters

You must use the Action parameter to specify the operation that you want to perform. For example, to create a file system, specify the parameter as Action=CreateFileSystem. You must also specify other request parameters based on the operations and common request parameters. For more information, see Common request parameters.

Encoding format

All requests and responses are encoded in UTF-8.