Release Notes
Announcements
The API supports access from either a nearby region (at dc.intl.tencentcloudapi.com) or a specified region (at dc.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 "dc.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) | dc.intl.tencentcloudapi.com |
| South China (Guangzhou) | dc.ap-guangzhou.tencentcloudapi.com |
| East China (Shanghai) | dc.ap-shanghai.tencentcloudapi.com |
| East China (Nanjing) | dc.ap-nanjing.tencentcloudapi.com |
| North China (Beijing) | dc.ap-beijing.tencentcloudapi.com |
| Southwest China (Chengdu) | dc.ap-chengdu.tencentcloudapi.com |
| Southwest China (Chongqing) | dc.ap-chongqing.tencentcloudapi.com |
| Hong Kong, Macao, Taiwan (Hong Kong, China) | dc.ap-hongkong.tencentcloudapi.com |
| Southeast Asia (Singapore) | dc.ap-singapore.tencentcloudapi.com |
| Southeast Asia (Jakarta) | dc.ap-jakarta.tencentcloudapi.com |
| Southeast Asia (Bangkok) | dc.ap-bangkok.tencentcloudapi.com |
| Northeast Asia (Seoul) | dc.ap-seoul.tencentcloudapi.com |
| Northeast Asia (Tokyo) | dc.ap-tokyo.tencentcloudapi.com |
| U.S. East Coast (Virginia) | dc.na-ashburn.tencentcloudapi.com |
| U.S. West Coast (Silicon Valley) | dc.na-siliconvalley.tencentcloudapi.com |
| South America (São Paulo) | dc.sa-saopaulo.tencentcloudapi.com |
| Europe (Frankfurt) | dc.eu-frankfurt.tencentcloudapi.com |
All the Tencent Cloud APIs communicate via HTTPS, providing highly secure communication tunnels.
Supported HTTP request methods:
The Content-Type types supported by POST requests:
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.
Only UTF-8 encoding is used.
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback