tencent cloud

私有网络

动态与公告
产品动态
产品公告
腾讯云网络总览
产品简介
产品概述
产品优势
应用场景
基本概念
配额限制
购买指南
计费概述
欠费说明
快速入门
网络规划
VPC 连接
快速搭建 IPv4 私有网络
操作指南
网络拓扑
网络性能大盘
私有网络
子网
路由表
弹性公网 IP
高可用虚拟 IP
弹性网卡
共享带宽包
网络连接
安全管理
诊断工具
告警与监控
实践教程
查看单地域按流量计费的总带宽
基础网络迁移至私有网络
安全组变更最佳实践
配置云服务器为公网网关
用 HAVIP+Keepalived 搭建高可用主备集群
通过专线接入和 VPN 连接实现混合云主备冗余通信
通过云联网和 VPN 连接实现混合云主备冗余通信
通过 EIP 实现云服务器访问 Internet
故障处理
无法删除 VPC 或子网
使用云联网打通两个 VPC 后网络不通
同 VPC 下两台云服务器无法 ping 通
API 文档
History
Introduction
API Category
Making API Requests
VPC APIs
Route Table APIs
Elastic Public IP APIs
Elastic IPv6 APIs
Highly Available Virtual IP APIs
ENI APIs
Bandwidth Package APIs
NAT Gateway APIs
Direct Connect Gateway APIs
Cloud Connect Network APIs
Network ACL APIs
Network Parameter Template APIs
Network Detection-Related APIs
Flow Log APIs
Gateway Traffic Monitor APIs
Private Link APIs
Traffic Mirroring APIs
Other APIs
Subnet APIs
VPN Gateway APIs
Security Group APIs
Snapshot Policy APIs
Error Codes
Data Types
常见问题
通用类
连接类
安全类
联系我们
词汇表

Request Structure

PDF
聚焦模式
字号
最后更新时间: 2026-03-31 17:00:58

1. Service Address

The API supports access from either a nearby region (at vpc.intl.tencentcloudapi.com) or a specified region (at vpc.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 "vpc.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) vpc.intl.tencentcloudapi.com
South China (Guangzhou) vpc.ap-guangzhou.tencentcloudapi.com
East China (Shanghai) vpc.ap-shanghai.tencentcloudapi.com
East China (Nanjing) vpc.ap-nanjing.tencentcloudapi.com
North China (Beijing) vpc.ap-beijing.tencentcloudapi.com
Southwest China (Chengdu) vpc.ap-chengdu.tencentcloudapi.com
Southwest China (Chongqing) vpc.ap-chongqing.tencentcloudapi.com
Hong Kong, Macao, Taiwan (Hong Kong, China) vpc.ap-hongkong.tencentcloudapi.com
Southeast Asia (Singapore) vpc.ap-singapore.tencentcloudapi.com
Southeast Asia (Jakarta) vpc.ap-jakarta.tencentcloudapi.com
Southeast Asia (Bangkok) vpc.ap-bangkok.tencentcloudapi.com
Northeast Asia (Seoul) vpc.ap-seoul.tencentcloudapi.com
Northeast Asia (Tokyo) vpc.ap-tokyo.tencentcloudapi.com
U.S. East Coast (Virginia) vpc.na-ashburn.tencentcloudapi.com
U.S. West Coast (Silicon Valley) vpc.na-siliconvalley.tencentcloudapi.com
South America (São Paulo) vpc.sa-saopaulo.tencentcloudapi.com
Europe (Frankfurt) vpc.eu-frankfurt.tencentcloudapi.com

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 of the financial availability zone, preferably in the same region as specified in Region.

Access region for financial availability zone Domain name for financial availability zone
East China (Shanghai Finance) vpc.ap-shanghai-fsi.tencentcloudapi.com
South China (Shenzhen Finance) vpc.ap-shenzhen-fsi.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.

帮助和支持

本页内容是否解决了您的问题?

填写满意度调查问卷,共创更好文档体验。

文档反馈