Request Structure

Last updated: 2019-11-29 16:28:39

1. Service Address

The API supports access from either a nearby region (at or a specified region (at for Guangzhou, for example).

It is recommended to use the domain name for nearby access. Based on the location of the client when calling the API, the request will be automatically resolved to the server in the nearest region. For example, if a request is initiated in Guangzhou, it will be automatically resolved to the server in Guangzhou, and the effect is the same as that when specifying

Note: For latency-sensitive businesses, it is recommended to specify a domain name with region.

Below lists the currently supported regions:

Access region Domain name
Local access region (recommended, only 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)
Access region for financial availability zone Domain name for financial availability zone
East China (Shanghai Financial)
South China (Shenzhen Financial)

2. Communications Protocol

All the TencentCloud 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). You must use TC3-HMAC-SHA256 to calculate the signature.
  • application/x-www-form-urlencoded. You must use HmacSHA1 or HmacSHA256 to calculate the signature.
  • multipart/form-data (only supported by certain APIs).You must use TC3-HMAC-SHA256 to calculate the signature.

The packet size of a GET request cannot exceed 32 KB. Every POST request signed with HmacSHA1 or HmacSHA256 signatures must have a size no larger than 1 MB. POST requests that signed with TC3-HMAC-SHA256 signatures can have a size up to 10 MB.

4. Character Encoding

Only UTF-8 encoding can be used.