tencent cloud

TencentDB for DBbrain

Release Notes and Announcements
Release Notes
Announcements
Product Introduction
Overview
Features
Strengths
Use Cases
Feature List
Region List
Purchase Guide
Operation Guide
Cloud Access Management
Self-Built Database Access
Instance Overview
Instance Management
Monitoring and Alarms
Health Report and Kill Session Report Management
MySQL/TDSQL-C for MySQL Performance Optimization
TDSQL for MySQL/MariaDB Performance Optimization
Distributed cache database (Distributed Cache) diagnostic optimization
MongoDB Performance Optimization
Full-Link Analysis
Practical Tutorial
Fixing High CPU Utilization on MySQL Instance
Fixing Lock Conflict on MySQL Instance
How to Address High CPU Utilization Issues in Distributed Cache Instances
Fixing High CPU Utilization in MongoDB Instance
Fixing Short Node Oplog Retention Period in MongoDB Instance
API Documentation
History
Introduction
Introduction
API Category
Making API Requests
Session Killing APIs
Exception Detection APIs
Other APIs
Redis related APIs
Health Report Email Sending APIs
Space Analysis APIs
Slow Log Analysis APIs
Security Audit APIs
Database Audit APIs
Data Types
Error Codes
DBbrain APIs 2019-10-16
FAQs
Self-Built Database Issues
MySQL Performance
Product
Service Level Agreement
Glossary
Contact Us

Request Structure

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2025-10-24 14:50:16

1. Service Address

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