Request Structure

Last updated: 2019-11-29 18:07:17


1. Service Address

In this product, your API requests are routed to the nearest server via the domain name You can also access APIs using the domain name for specified region, such as for Guangzhou region.

It is recommended to use the domain name for accessing the nearest server. When you call an API, this domain name is automatically resolved to a server in a region nearest to the client where the API is initiated. For example, when you initiate an API request in Guangzhou, this domain name is automatically resolved to a Guangzhou server, with the result same as that of using "".

Note: For business sensitive to latency, it is recommended to specify domain names containing the region.

The supported domain names are listed as below:

Region Domain Name
Accessing the nearest server (recommended, and is only for non-Finance regions)
South China (Guangzhou)
East China (Shanghai)
North China (Beijing)
Southwest China (Chengdu)
Southwest China (Chongqing)
China (Hong Kong)
Southeast Asia (Singapore)
Asia Pacific (Bangkok)
Asia Pacific (Mumbai)
Asia Pacific (Seoul)
Asia Pacific (Tokyo)
Eastern U.S. (Virginia)
Western U.S. (Silicon Valley)
North America (Toronto)
Europe (Frankfurt)
Europe (Moscow)

Note: Finance regions and non-Finance regions are isolated from each other. Therefore, when you access the services in a finance region (the common parameter Region is finance region), you need to specify a domain name containing the region specified in the Region field.

Finance Region Domain Name
East China (Shanghai Finance)
South China (Shenzhen Finance)

2. Communication Protocol

All Tencent Cloud APIs communicate over HTTPS to provide high-security channels.

3. Request Methods

Supported HTTP request method:

  • POST (recommended)
  • GET

Content-Type supported by POST request:

  • application/json (recommended). The TC3-HMAC-SHA256 signature method is required.
  • application/x-www-form-urlencoded. The HmacSHA1 or HmacSHA256 signature methods are required.
  • multipart/form-data (supported only in some APIs). The TC3-HMAC-SHA256 signature method is required.

The length of a GET request cannot exceed 32 KB. The length of a POST request using the HmacSHA1 and HmacSHA256 signature methods cannot exceed 1 MB.

4. Character Encoding

UTF-8 encoding is always used.