Request Structure

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


1. Hosted Regions

You can choose to send API requests from either a nearby region (at or a specified region (for example, go to to select Guangzhou as the hosted region).

We recommended that you call the nearest API server.
Your API request will be automatically resolved to a server that is nearest to the client. For example, if you make an API request from Guangzhou, the request will be automatically resolved to the server in Guangzhou that works the same as to include 'guangzhou' in the request (

*Note: For latency-sensitive businesses, we recommend that you specify the hosted region in the domain name. *

Tencent Cloud currently supports the following hosted regions:

Hosted region Domain name
Nearby hosted region (recommended, only available for non-financial availability zones)
South China (Guangzhou)
East China (Shanghai)
North China (Beijing)
Southwest China (Chengdu)
Southwest China (Chongqing)
Southeast Asia (Hong Kong, China)
Southeast Asia (Singapore)
Asia Pacific (Bangkok)
Asia Pacific (Mumbai)
Asia Pacific (Seoul)
Asia Pacific (Tokyo)
Eastern America (Virginia)
Western America (Silicon Valley)
North America (Toronto)
Europe (Frankfurt)
Europe (Moscow)

Note: As financial availability zones and non-financial availability zones are isolated, when accessing the services in a financial availability zone (with the common parameter Region specifying a financial availability zone), it is necessary to specify a domain name with the financial availability zone, preferably in the same region as specified in Region.

Hosted region for financial availability zone Domain name for financial availability zone
East China (Shanghai Financial)
South China (Shenzhen Financial)

2. Communications Protocol

All the Tencent Cloud APIs communicate via HTTPS, providing highly secure communications tunnels.

3. Request Method

Supported HTTP request methods:

  • POST (recommended)
  • GET

The Content-Type types supported by POST request:

  • application/json (recommended). The TC3-HMAC-SHA256 signature method must be used.
  • application/x-www-form-urlencoded. The HmacSHA1 or HmacSHA256 signature method must be used.
  • multipart/form-data (only supported by certain APIs). The TC3-HMAC-SHA256 signature method must be used.

The request packet size of a GET request cannot exceed 32 KB. A POST request cannot exceed 1 MB when the HmacSHA1 or HmacSHA256 signature method is used. A POST request can be up to 10 MB when the TC3-HMAC-SHA256 signature method is used.

4. Character Encoding

Only UTF-8 encoding is used.