The API supports access from either a nearby region (at eb.tencentcloudapi.com) or a specified region (at eb.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 "eb.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)||eb.tencentcloudapi.com|
|South China (Guangzhou)||eb.ap-guangzhou.tencentcloudapi.com|
|East China (Shanghai)||eb.ap-shanghai.tencentcloudapi.com|
|North China (Beijing)||eb.ap-beijing.tencentcloudapi.com|
|Southwest China (Chengdu)||eb.ap-chengdu.tencentcloudapi.com|
|Southwest China (Chongqing)||eb.ap-chongqing.tencentcloudapi.com|
|Hong Kong, Macao, Taiwan (Hong Kong, China)||eb.ap-hongkong.tencentcloudapi.com|
|Southeast Asia (Singapore)||eb.ap-singapore.tencentcloudapi.com|
|Southeast Asia (Bangkok)||eb.ap-bangkok.tencentcloudapi.com|
|South Asia (Mumbai)||eb.ap-mumbai.tencentcloudapi.com|
|Northeast Asia (Seoul)||eb.ap-seoul.tencentcloudapi.com|
|Northeast Asia (Tokyo)||eb.ap-tokyo.tencentcloudapi.com|
|U.S. East Coast (Virginia)||eb.na-ashburn.tencentcloudapi.com|
|U.S. West Coast (Silicon Valley)||eb.na-siliconvalley.tencentcloudapi.com|
|North America (Toronto)||eb.na-toronto.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.