tencent cloud

TencentDB for MySQL

Tutorial Pengguna
Pengenalan Produk
Ikhtisar
Keunggulan
Kasus Penggunaan
Database Architecture
Kebijakan Isolasi Sumber Daya
Database Instance
Ketersediaan Tinggi (Beberapa AZ)
Wilayah dan AZ
Panduan Pembelian
Ikhtisar Penagihan
Metode Pembelian
Pembayaran Jatuh Tempo
Pengembalian Dana
Biaya Penyesuaian Instans
Penagihan Ruang Cadangan
Memulai
Ikhtisar
Membuat Instans MySQL
Panduan Operasi
Batas Penggunaan
Ikhtisar Operasi
Manajemen dan Pemeliharaan Instans
Peningkatan Versi
Memperluas Instans
Proksi Database
Manajemen Akun
Konfigurasi Parameter
Pencadangan dan Pengembalian
Migrasi data
Jaringan dan Keamanan
Pemantauan dan Alarm
Pusat Log
Tag
Laporan Resmi
Laporan Resmi Keamanan
Service Agreement
Service Level Agreement
Terms of Service
DokumentasiTencentDB for MySQL

Request Structure

Mode fokus
Ukuran font
Terakhir diperbarui: 2026-03-19 18:22:06

1. Service Address

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

Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan