NAS API requests are in a unified structure.


The endpoint of NAS APIs follows a format of and nas. [RegionId.]

Specifically, RegionId refers to the service region. You can call the API of the designated region based on your own region. The service is available in the following regions.

Region RegionId Endpoint
Beijing cn-beijing
Shanghai cn-shanghai
Hangzhou cn-hangzhou
Shenzhen cn-shenzhen
Qingdao cn-qingdao
Zhangjiakou cn-zhangjiakou
Hohhot cn-huhehaote
Chengdu cn-chengdu
China (Hong Kong) cn-hongkong
Singapore ap-southeast-1
Sydney ap-southeast-2
Kuala Lumpur ap-southeast-3
Jakarta ap-southeast-5
Tokyo ap-northeast-1
Mumbai ap-south-1
Frankfurt eu-central-1
London eu-west-1
Silicon Valley us-west-1
Virginia us-east-1

Communication protocol

HTTP and HTTPS protocols are supported for request communications. We recommend that you use an HTTPS channel which provides higher security.

Request methods

NAS API supports sending HTTP GET requests. Using this method, you are required to include request parameters in the request URL.

Request parameters

Each request must specify the operation to be executed, namely the Action parameter (such as DescribeRegions). Each operation must contain the common request parameters and the specific request parameters of the specified operation.

Character encoding

Requests and responses are both encoded using the UTF-8 character set.


JAVA, PHP, and, Python SDKs are currently supported.

We recommend that you use SDKs which can simplify the process for HTTP message encapsulation and signature operations.

You can download the SDK from the following links: