tencent cloud


Request Structure

Last updated: 2022-03-28 10:49:01

1. Service Address

The API supports access from either a nearby region (at tms.tencentcloudapi.com) or a specified region (at tms.ap-guangzhou.tencentcloudapi.com for Guangzhou, for example).

We recommend using the domain name to access the nearest server. When you call an API, the request is automatically resolved to a server in the region nearest to the location 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, the result is the same as that of specifying the region in the domain like "tms.ap-guangzhou.tencentcloudapi.com".

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

Tencent Cloud currently supports the following regions:

Hosted region Domain name
Local access region (recommended, only for non-financial availability zones) tms.tencentcloudapi.com
South China (Guangzhou) tms.ap-guangzhou.tencentcloudapi.com
East China (Shanghai) tms.ap-shanghai.tencentcloudapi.com
North China (Beijing) tms.ap-beijing.tencentcloudapi.com
Southwest China (Chengdu) tms.ap-chengdu.tencentcloudapi.com
Southwest China (Chongqing) tms.ap-chongqing.tencentcloudapi.com
Hong Kong, Macao, Taiwan (Hong Kong, China) tms.ap-hongkong.tencentcloudapi.com
Southeast Asia (Singapore) tms.ap-singapore.tencentcloudapi.com
Southeast Asia (Bangkok) tms.ap-bangkok.tencentcloudapi.com
South Asia (Mumbai) tms.ap-mumbai.tencentcloudapi.com
Northeast Asia (Seoul) tms.ap-seoul.tencentcloudapi.com
Northeast Asia (Tokyo) tms.ap-tokyo.tencentcloudapi.com
U.S. East Coast (Virginia) tms.na-ashburn.tencentcloudapi.com
U.S. West Coast (Silicon Valley) tms.na-siliconvalley.tencentcloudapi.com
North America (Toronto) tms.na-toronto.tencentcloudapi.com
Europe (Frankfurt) tms.eu-frankfurt.tencentcloudapi.com
Europe (Moscow) tms.eu-moscow.tencentcloudapi.com

2. Communications Protocol

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

3. Request Methods

Supported HTTP request methods:

  • POST (recommended)
  • GET

The Content-Type types supported by POST requests:

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

The size of a GET request packet is up to 32 KB. The size of a POST request is up to 1 MB when the HmacSHA1 or HmacSHA256 signature algorithm is used, and up to 10 MB when TC3-HMAC-SHA256 is used.

4. Character Encoding

Only UTF-8 encoding is used.

Contact Us

Contact our sales team or business advisors to help your business.

Technical Support

Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

7x24 Phone Support